LiveActive security incident?Get immediate response
CVE Record

CVE-2018-12886: stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (...

stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (GCC) 4.1 through 8 (under certain circumstances) generate instruction sequences when targeting ARM targets that spill the address of the stack protector guard, which allows an attacker to bypass the protection of -fstack-protector, -fstack-protector-all, -fstack-protector-strong, and -fstack-protector-explicit against stack overflow by controlling what the stack canary is compared against.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a compiler-generated weakness, not a normal application bug. Certain GCC 4.1 through 8 ARM builds could produce stack-protector code that can be bypassed, reducing a key defense against stack overflows in affected binaries.

Executive priority

Prioritize inventory and rebuild planning for ARM software supply chains. Urgency is higher for exposed embedded products, appliances, and firmware, but evidence here does not support claims of active exploitation.

Technical view

For ARM targets, GCC functions stack_protect_prologue and stack_protect_epilogue may spill the stack protector guard address. If an attacker can influence the relevant stack state, protected binaries may compare against an attacker-controlled canary value, weakening -fstack-protector variants.

Likely exposure

Exposure is most likely in ARM firmware, embedded software, or applications compiled with GCC 4.1 through 8 using stack protector options. The bundle does not identify specific downstream products or distributions.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. Practical exploitation would require a separate stack overflow condition plus circumstances allowing the stack protector comparison to be bypassed.

Researcher notes

The CVE describes a code-generation flaw in GCC’s ARM stack protector sequence. Evidence is limited to the CVE record and GCC references; no CVSS, CWE, affected CPEs, or public exploit status are provided in the bundle.

Mitigation direction

  • Inventory ARM-targeted GCC toolchains used for production builds.
  • Check GNU GCC and downstream vendor guidance for the relevant fixed compiler version.
  • Rebuild affected ARM binaries with a corrected toolchain when available.
  • Prioritize binaries exposed to untrusted input or safety-critical workflows.
  • Retain layered mitigations such as ASLR and memory-safe rewrites where feasible.

Validation and detection

  • Identify ARM binaries built with GCC 4.1 through 8.
  • Confirm whether stack protector options were enabled in those builds.
  • Map each binary to compiler provenance and downstream patch level.
  • Review GCC change notes and vendor advisories for fix confirmation.
  • Treat vulnerable compiler output as exposure; avoid exploit-based validation.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-12886 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.