CVE-2023-4039General(gnu / gcc)

LOWCVSS 4.8 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

**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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-693

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • gcc

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • General: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
gcc

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-06-11: 1Technical Details · 2026-06-11: 106-11
Signal classification1 categories
General
1100.0%
Full discourse1 post
  • Geoffrey Irving@geoffreyirving
    General

    Via Opus 4.8, not checked carefully. Delightfully, Fable refused to help me. :) 1. CVE-2019-0546 is a Visual Studio example 2. CVE-2023-4039 is a gcc bug where the compiler fails to add hardening (so exploitable if you needed that hardening) I agree they are rare, though! But the claim is not that these specific projects are the highest priority, but that we will be able to do projects of this scale, including many other projects which do result in piles of vulnerabilities.

    Post summary

    The post briefly mentions two CVEs, noting a gcc hardening bug, but provides no PoC, exploit code, patch, or evidence of active exploitation.

    0002076
    13.2K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appgnugcc--arm64

Explore more