CVE-2015-3166
Published: 22 May 2015
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.
Priority
Status
Package | Release | Status |
---|---|---|
postgresql-8.4 Launchpad, Ubuntu, Debian |
precise |
Ignored
(end of life)
|
trusty |
Does not exist
|
|
upstream |
Needs triage
|
|
utopic |
Does not exist
|
|
vivid |
Does not exist
|
|
wily |
Does not exist
|
|
xenial |
Does not exist
|
|
yakkety |
Does not exist
|
|
zesty |
Does not exist
|
|
postgresql-9.1 Launchpad, Ubuntu, Debian |
precise |
Released
(9.1.16-0ubuntu0.12.04)
|
trusty |
Released
(9.1.16-0ubuntu0.14.04)
|
|
upstream |
Released
(9.1.16)
|
|
utopic |
Does not exist
|
|
vivid |
Does not exist
|
|
wily |
Does not exist
|
|
xenial |
Does not exist
|
|
yakkety |
Does not exist
|
|
zesty |
Does not exist
|
|
postgresql-9.3 Launchpad, Ubuntu, Debian |
precise |
Does not exist
|
trusty |
Released
(9.3.7-0ubuntu0.14.04)
|
|
upstream |
Released
(9.3.7)
|
|
utopic |
Does not exist
|
|
vivid |
Does not exist
|
|
wily |
Does not exist
|
|
xenial |
Does not exist
|
|
yakkety |
Does not exist
|
|
zesty |
Does not exist
|
|
postgresql-9.4 Launchpad, Ubuntu, Debian |
precise |
Does not exist
|
trusty |
Does not exist
|
|
upstream |
Released
(9.4.2)
|
|
utopic |
Released
(9.4.2-0ubuntu0.14.10)
|
|
vivid |
Released
(9.4.2-0ubuntu0.15.04)
|
|
wily |
Released
(9.4.2-1)
|
|
xenial |
Does not exist
|
|
yakkety |
Does not exist
|
|
zesty |
Does not exist
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 9.8 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |