LiveActive security incident?Get immediate response
CVE Record

CVE-2015-3166: The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x be...

The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 does not properly handle system-call errors, which allows attackers to obtain sensitive information or have other unspecified impact via unknown vectors, as demonstrated by an out-of-memory error.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older PostgreSQL releases contain a low-level formatting bug that can mishandle system-call failures. The public record says this may expose sensitive information or cause other unspecified impact, but it does not explain a practical attack path. Organizations still running these obsolete versions should treat this as upgrade-driven risk. Exposure is most likely in legacy PostgreSQL 9.0 through 9.4 deployments, including systems pinned to old Debian or Ubuntu packages. Modern supported PostgreSQL versions are not listed as affected in the provided sources. Schedule remediation for any remaining affected PostgreSQL instances. The vulnerability record is sparse, but the affected software is database infrastructure and the listed versions are very old, increasing operational and compliance risk. Mitigation focus: Upgrade PostgreSQL to the fixed release for the deployed branch or a supported newer version.; Apply relevant Debian or Ubuntu security updates where PostgreSQL is OS-packaged.; Prioritize externally reachable or multi-tenant database environments first..

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-2015-3166 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
1Source 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
PostgreSQL Global Development GroupPostgreSQLbefore 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2Listed
Weakness

CWE details

No CWE listed

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