LiveActive security incident?Get immediate response
CVE Record

CVE-2012-3488: The libxslt support in contrib/xml2 in PostgreSQL 8.3 before 8.3.20, 8.4 before 8.4.13, 9.0 before 9.0.9, a...

The libxslt support in contrib/xml2 in PostgreSQL 8.3 before 8.3.20, 8.4 before 8.4.13, 9.0 before 9.0.9, and 9.1 before 9.1.5 does not properly restrict access to files and URLs, which allows remote authenticated users to modify data, obtain sensitive information, or trigger outbound traffic to arbitrary external hosts by leveraging (1) stylesheet commands that are permitted by the libxslt security options or (2) an xslt_process feature, related to an XML External Entity (aka XXE) issue.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw affects old PostgreSQL releases when the optional xml2/libxslt functionality is available. An authenticated database user could make XML/XSLT processing access files, leak sensitive information, modify data, or cause outbound connections. It is not listed as KEV, and the provided sources do not show active exploitation. Exposure is most likely in legacy PostgreSQL 8.3, 8.4, 9.0, or 9.1 deployments using contrib/xml2 where authenticated users can execute XML/XSLT processing features. Systems without xml2/libxslt exposure or without untrusted database users appear less exposed based on the source description. Treat as high priority for legacy PostgreSQL environments, especially shared databases or applications with semi-trusted database users. The main urgency is protecting data confidentiality and integrity, not responding to confirmed active exploitation. Mitigation focus: Upgrade affected PostgreSQL branches to the fixed releases or vendor-patched packages.; Prioritize systems where untrusted users can authenticate to the database.; Disable or remove contrib/xml2 where it is not operationally required..

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-2012-3488 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.

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.