LiveActive security incident?Get immediate response
CVE Record

CVE-2012-6089: Multiple stack-based buffer overflows in the canoniseFileName function in os/pl-os.c in SWI-Prolog before 6...

Multiple stack-based buffer overflows in the canoniseFileName function in os/pl-os.c in SWI-Prolog before 6.2.5 and 6.3.x before 6.3.7 allow remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted filename.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

SWI-Prolog had stack buffer overflows in filename canonicalisation before fixed 6.2.5 and 6.3.7 releases. If an exposed application lets users influence filenames, a crafted filename could crash the process and may allow code execution. Treat internet-facing or automation-facing Prolog services as higher priority. Exposure is most likely where SWI-Prolog or pl processes handle untrusted filenames, paths, uploads, generated file references, or user-controlled project paths. Internal batch systems may still be exposed if they process external data. General installations with no untrusted filename input have lower practical exposure. Prioritize remediation for systems where SWI-Prolog processes external files or paths. The main confirmed risk is service crash, with possible code execution noted by the CVE. Lack of KEV evidence lowers emergency pressure, but legacy vulnerable versions should not remain in exposed workflows. Mitigation focus: Upgrade SWI-Prolog to 6.2.5, 6.3.7, or a later supported release.; Prioritize exposed services that pass user-controlled filenames to SWI-Prolog.; Check distribution advisories, including Red Hat guidance, for packaged fixed versions..

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2012-6089 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.