LiveActive security incident?Get immediate response
CVE Record

CVE-1999-1111: Vulnerability in StackGuard before 1.21 allows remote attackers to bypass the Random and Terminator Canary...

Vulnerability in StackGuard before 1.21 allows remote attackers to bypass the Random and Terminator Canary security mechanisms by using a non-linear attack which directly modifies a pointer to a return address instead of using a buffer overflow to reach the return address entry itself.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

StackGuard is an old compiler defense that adds a hidden "tripwire" value on the stack to catch buffer overflow attacks. Versions before 1.21 could be bypassed by an attacker who overwrites a pointer that later gets written to, letting them redirect program execution without disturbing the tripwire. This is a legacy issue from 1999 in developer tooling, not a modern product vulnerability. Exposure is minimal for modern environments. StackGuard was an Immunix/GCC compiler extension from the late 1990s; contemporary toolchains use successors such as ProPolice/SSP, along with ASLR, DEP/NX, and CFI. Only systems still building or running binaries produced by pre-1.21 StackGuard would be affected, which is exceptionally rare today. Low priority for modern enterprises. Treat as historical toolchain hygiene rather than an active incident. Only escalate if an audit surfaces legacy Immunix/StackGuard build systems still in production. Mitigation focus: Rebuild affected binaries with a modern stack protector such as GCC/Clang -fstack-protector-strong.; Enable ASLR, DEP/NX, and Control Flow Integrity on hosts running legacy compiled software.; Retire or isolate any systems still dependent on StackGuard-era Immunix toolchains..

Prepared

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-1999-1111 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
2Source 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.