CVE-2015-3166
CVE-2015-3166 Vulnerability Analysis & Exploit Intelligence
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.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
5%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
References
9 on the record
- www.postgresql.org/about/news/1587/
x_refsource_MISC
- www.postgresql.org/docs/9.0/static/release-9-0-20.html
x_refsource_MISC
- www.postgresql.org/docs/9.1/static/release-9-1-16.html
x_refsource_MISC
- www.postgresql.org/docs/9.2/static/release-9-2-11.html
x_refsource_MISC
- www.postgresql.org/docs/9.3/static/release-9-3-7.html
x_refsource_MISC
- www.postgresql.org/docs/9.4/static/release-9-4-2.html
x_refsource_MISC
- www.debian.org/security/2015/dsa-3269
x_refsource_MISC
- www.debian.org/security/2015/dsa-3270
x_refsource_MISC
Elsewhere on this site
- postgresql global development groupevery CVE for this vendor
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.