CVE-2023-4039: GCC's-fstack-protector fails to guard dynamically-sized local variables on AArch64
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 63.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Azure Linux 3.0 ARM 13.2.0-7; Azure Linux 3.0 x64 13.2.0-7; CBL Mariner 2.0 ARM 11.2.0-6.
Low priority for now. Upgrade to Azure Linux 3.0 ARM 13.2.0-7; Azure Linux 3.0 x64 13.2.0-7; CBL Mariner 2.0 ARM 11.2.0-6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
**DISPUTED**A failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables. The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.
- Published
- Sep 13, 2023
- Updated
- Oct 14, 2026
- EPSS
- 1.0% · 63th percentile
- CWE
- CWE-693
Report tools
Action score
19
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.8
- CNA · Arm
- 4.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnu | gcc | cpe:2.3:a:gnu:gcc |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnu gccbefore 2023-09-12
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Arm). Independent of NVD's CPE analysis and usually ahead of it.
Arm Ltd Arm GNU Toolchain
- All versions where option -fstack-protector is usedaffected
GNU GCC
- All versions of GCC that target AArch64 when option -fstack-protector is usedaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.19 | gcc | before 13.2.1_git20231014-r0 | 13.2.1_git20231014-r0 |
| Debian:12 | gcc-11 | from 0 | — |
| Debian:12 | gcc-12 | before 12.2.0-14+deb12u1 | 12.2.0-14+deb12u1 |
| Debian:13 | gcc-12 | before 12.3.0-9 | 12.3.0-9 |
| Debian:13 | gcc-13 | before 13.2.0-4 | 13.2.0-4 |
| openSUSE:Leap 15.4 | cross-nvptx-gcc12 | before 12.3.0+git1204-150000.1.16.1 | 12.3.0+git1204-150000.1.16.1 |
| openSUSE:Leap 15.4 | cross-nvptx-gcc13 | before 13.2.1+git7813-150000.1.3.2 | 13.2.1+git7813-150000.1.3.2 |
| openSUSE:Leap 15.4 | cross-nvptx-gcc13 | before 13.2.1+git7813-150000.1.6.1 | 13.2.1+git7813-150000.1.6.1 |
| openSUSE:Leap 15.4 | gcc12-testresults | before 12.3.0+git1204-150000.1.16.1 | 12.3.0+git1204-150000.1.16.1 |
| openSUSE:Leap Micro 5.3 | gcc12 | before 12.3.0+git1204-150000.1.16.1 | 12.3.0+git1204-150000.1.16.1 |
| openSUSE:Leap Micro 5.3 | gcc13 | before 13.2.1+git7813-150000.1.3.3 | 13.2.1+git7813-150000.1.3.3 |
| openSUSE:Leap Micro 5.3 | gcc13 | before 13.2.1+git7813-150000.1.6.1 | 13.2.1+git7813-150000.1.6.1 |
| openSUSE:Tumbleweed | gcc12 | before 12.3.0+git1204-2.1 | 12.3.0+git1204-2.1 |
| openSUSE:Tumbleweed | gcc13 | before 13.2.1+git7813-1.1 | 13.2.1+git7813-1.1 |
| openSUSE:Tumbleweed | gcc7 | before 7.5.0+r278197-15.1 | 7.5.0+r278197-15.1 |
| SUSE:Linux Enterprise Installer Updates 15 SP1 | gcc12 | before 12.3.0+git1204-150000.1.16.1 | 12.3.0+git1204-150000.1.16.1 |
| SUSE:Linux Enterprise Installer Updates 15 SP1 | gcc13 | before 13.2.1+git7813-150000.1.6.1 | 13.2.1+git7813-150000.1.6.1 |
| SUSE:Linux Enterprise Installer Updates 15 SP2 | gcc13 | before 13.2.1+git7813-150000.1.3.3 | 13.2.1+git7813-150000.1.3.3 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP4 | gcc7 | before 7.5.0+r278197-150000.4.35.1 | 7.5.0+r278197-150000.4.35.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | cross-nvptx-gcc12 | before 12.3.0+git1204-150000.1.16.1 | 12.3.0+git1204-150000.1.16.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | cross-nvptx-gcc13 | before 13.2.1+git7813-150000.1.3.2 | 13.2.1+git7813-150000.1.3.2 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | cross-nvptx-gcc13 | before 13.2.1+git7813-150000.1.6.1 | 13.2.1+git7813-150000.1.6.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | gcc12-testresults | before 12.3.0+git1204-150000.1.16.1 | 12.3.0+git1204-150000.1.16.1 |
| SUSE:Linux Enterprise Module for Toolchain 12 | cross-nvptx-gcc12 | before 12.3.0+git1204-1.13.1 | 12.3.0+git1204-1.13.1 |
+6
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-12886stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (GCC) 4.1 through 8 (under certain33Monitor
- CVE-2002-2439Integer overflow in the new[] operator in gcc before 4.8.0 allows attackers to have unspecified impacts.31Monitor
- CVE-2019-15847The POWER9 backend in GNU Compiler Collection (GCC) before version 10 could optimize multiple calls of the __builtin_darn intrinsic into a s31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-46195Jan 14, 2022 · GCC v12.0 was discovered to contain an uncontrolled recursion via the component libiberty/rust-demangle.c.22Monitor
- ← EarlierCVE-2022-27943Mar 26, 2022 · libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.22Monitor
- ← EarlierCVE-2021-3826Sep 1, 2022 · Heap/stack buffer overflow in the dlang_lname function in d-demangle.c in libiberty allows attackers to potentially cause a denial of servic26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Azure Linux 3.0 ARM | 13.2.0-7 · gcc | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 13.2.0-7 · gcc | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 11.2.0-6 · gcc | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 11.2.0-6 · gcc | Microsoft (MSRC) |
| alpine:gcc | 13.2.1_git20231014-r0 · Alpine:v3.19 | Package registry (OSV) |
| debian:gcc-12 | 12.2.0-14+deb12u1 · Debian:12 | Package registry (OSV) |
| debian:gcc-13 | 13.2.0-4 · Debian:13 | Package registry (OSV) |
| opensuse:cross-nvptx-gcc12 | 12.3.0+git1204-150000.1.16.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:cross-nvptx-gcc13 | 13.2.1+git7813-150000.1.3.2 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:gcc12 | 12.3.0+git1204-150000.1.16.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:gcc12-testresults | 12.3.0+git1204-150000.1.16.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:gcc13 | 13.2.1+git7813-150000.1.3.3 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:gcc7 | 7.5.0+r278197-15.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:cross-nvptx-gcc12 | 12.3.0+git1204-1.13.1 · SUSE:Linux Enterprise Module for Toolchain 12 | Package registry (OSV) |
| suse:cross-nvptx-gcc12 | 12.3.0+git1204-150000.1.16.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
| suse:cross-nvptx-gcc13 | 13.2.1+git7813-150000.1.3.2 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
| suse:cross-nvptx-gcc7 | 7.5.0+r278197-13.1 · SUSE:Linux Enterprise Module for Toolchain 12 | Package registry (OSV) |
| suse:gcc12 | 12.3.0+git1204-1.13.1 · SUSE:Linux Enterprise Module for Toolchain 12 | Package registry (OSV) |
| suse:gcc12 | 12.3.0+git1204-150000.1.16.1 · SUSE:Linux Enterprise Installer Updates 15 SP1 | Package registry (OSV) |
| suse:gcc12-testresults | 12.3.0+git1204-150000.1.16.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
| suse:gcc13 | 13.2.1+git7813-150000.1.3.3 · SUSE:Linux Enterprise Installer Updates 15 SP2 | Package registry (OSV) |
| suse:gcc7 | 7.5.0+r278197-13.1 · SUSE:Linux Enterprise Module for Toolchain 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Tom HebbMeta Red Team X and Maria Markstedter from Azeria Labsfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-693 · Protection Mechanism FailureCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Site TracingCAPEC-107likelihood: Medium · Very High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Escaping a Sandbox by Calling Code in Another LanguageCAPEC-237likelihood: Low · Very High
- Using Unpublished Interfaces or FunctionalityCAPEC-36likelihood: Medium · High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.