CVE-2016-5424
published 2016-12-09CVE-2016-5424: PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 might allow remote authenticated users with the…
PriorityP338high7.1CVSS 3.0
AVNACHPRLUIRSUCHIHAH
EPSS
4.61%
90.6th percentile
PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 might allow remote authenticated users with the CREATEDB or CREATEROLE role to gain superuser privileges via a (1) " (double quote), (2) \ (backslash), (3) carriage return, or (4) newline character in a (a) database or (b) role name that is mishandled during an administrative operation.
Affected
47 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| postgresql | postgresql | <= 9.1.22 | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
| postgresql | postgresql | — | — |
CVSS provenance
nvdv3.07.1HIGHCVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
nvdv2.04.6MEDIUMAV:N/AC:H/Au:S/C:P/I:P/A:P
osv8.3HIGH
vendor_ubuntu8.3HIGH
vendor_redhat7.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-9j99-5j9q-2gmp: PostgreSQL before 9
ghsa_unreviewed·2022-05-14
CVE-2016-5424 [HIGH] CWE-94 GHSA-9j99-5j9q-2gmp: PostgreSQL before 9
PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 might allow remote authenticated users with the CREATEDB or CREATEROLE role to gain superuser privileges via a (1) " (double quote), (2) \ (backslash), (3) carriage return, or (4) newline character in a (a) database or (b) role name that is mishandled during an administrative operation.
OSV
postgresql-9.1, postgresql-9.3, postgresql-9.5 vulnerabilities
osv·2016-08-18·CVSS 8.3
CVE-2016-5423 [HIGH] postgresql-9.1, postgresql-9.3, postgresql-9.5 vulnerabilities
postgresql-9.1, postgresql-9.3, postgresql-9.5 vulnerabilities
Heikki Linnakangas discovered that PostgreSQL incorrectly handled certain
nested CASE/WHEN expressions. A remote attacker could possibly use this
issue to cause PostgreSQL to crash, resulting in a denial of service.
(CVE-2016-5423)
Nathan Bossart discovered that PostgreSQL incorrectly handled special
characters in database and role names. A remote attacker could possibly use
this issue to escalate privileges. (CVE-2016-5424)
OSV
CVE-2016-5424: PostgreSQL before 9
osv·2016-08-11·CVSS 7.1
CVE-2016-5424 [HIGH] CVE-2016-5424: PostgreSQL before 9
PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 might allow remote authenticated users with the CREATEDB or CREATEROLE role to gain superuser privileges via a (1) " (double quote), (2) \ (backslash), (3) carriage return, or (4) newline character in a (a) database or (b) role name that is mishandled during an administrative operation.
Ubuntu
PostgreSQL vulnerabilities
vendor_ubuntu·2016-08-18·CVSS 8.3
CVE-2016-5423 [HIGH] PostgreSQL vulnerabilities
Title: PostgreSQL vulnerabilities
Summary: Several security issues were fixed in PostgreSQL.
Heikki Linnakangas discovered that PostgreSQL incorrectly handled certain
nested CASE/WHEN expressions. A remote attacker could possibly use this
issue to cause PostgreSQL to crash, resulting in a denial of service.
(CVE-2016-5423)
Nathan Bossart discovered that PostgreSQL incorrectly handled special
characters in database and role names. A remote attacker could possibly use
this issue to escalate privileges. (CVE-2016-5424)
Instructions: This update uses a new upstream release, which includes additional bug
fixes. After a standard system update you need to restart PostgreSQL to
make all the necessary changes.
Red Hat
postgresql: privilege escalation via crafted database and role names
vendor_redhat·2016-08-11·CVSS 7.1
CVE-2016-5424 [HIGH] CWE-20 postgresql: privilege escalation via crafted database and role names
postgresql: privilege escalation via crafted database and role names
PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 might allow remote authenticated users with the CREATEDB or CREATEROLE role to gain superuser privileges via a (1) " (double quote), (2) \ (backslash), (3) carriage return, or (4) newline character in a (a) database or (b) role name that is mishandled during an administrative operation.
A flaw was found in the way PostgreSQL client programs handled database and role names containing newlines, carriage returns, double quotes, or backslashes. By crafting such an object name, roles with the CREATEDB or CREATEROLE option could escalate their privileges to superuser when a superuser next executes maintenance with a
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-5424 postgresql: privilege escalation via crafted database and role names [fedora-all]
bugzilla·2016-08-11·CVSS 7.1
CVE-2016-5424 [HIGH] CVE-2016-5424 postgresql: privilege escalation via crafted database and role names [fedora-all]
CVE-2016-5424 postgresql: privilege escalation via crafted database and role names [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supp
Bugzilla
CVE-2016-5424 postgresql: privilege escalation via crafted database and role names
bugzilla·2016-08-04·CVSS 7.1
CVE-2016-5424 [HIGH] CVE-2016-5424 postgresql: privilege escalation via crafted database and role names
CVE-2016-5424 postgresql: privilege escalation via crafted database and role names
It was found that PostgreSQL client programs mishandle database and role names containing newlines, carriage returns, double quotes, or backslashes. By crafting such an object name, roles with the CREATEDB or CREATEROLE option could escalate their privileges to superuser when a superuser next executes maintenance with a vulnerable program. Vulnerable programs include pg_dumpall, pg_upgrade, vacuumdb, reindexdb, and clusterdb.
Discussion:
Acknowledgments:
Name: the PostgreSQL project
Upstream: Nathan Bossart
---
Public via:
https://www.postgresql.org/about/news/1688/
---
Created postgresql tracking bugs for this issue:
Affects: fedora-all [bug 1366346]
---
Upstream patch:
https://git.postgresql.o
http://rhn.redhat.com/errata/RHSA-2016-1781.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1820.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1821.htmlhttp://rhn.redhat.com/errata/RHSA-2016-2606.htmlhttp://www.debian.org/security/2016/dsa-3646http://www.securityfocus.com/bid/92435http://www.securitytracker.com/id/1036617https://access.redhat.com/errata/RHSA-2017:2425https://security.gentoo.org/glsa/201701-33https://www.postgresql.org/about/news/1688/https://www.postgresql.org/docs/current/static/release-9-1-23.htmlhttps://www.postgresql.org/docs/current/static/release-9-2-18.htmlhttps://www.postgresql.org/docs/current/static/release-9-3-14.htmlhttps://www.postgresql.org/docs/current/static/release-9-4-9.htmlhttps://www.postgresql.org/docs/current/static/release-9-5-4.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1781.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1820.htmlhttp://rhn.redhat.com/errata/RHSA-2016-1821.htmlhttp://rhn.redhat.com/errata/RHSA-2016-2606.htmlhttp://www.debian.org/security/2016/dsa-3646http://www.securityfocus.com/bid/92435http://www.securitytracker.com/id/1036617https://access.redhat.com/errata/RHSA-2017:2425https://security.gentoo.org/glsa/201701-33https://www.postgresql.org/about/news/1688/https://www.postgresql.org/docs/current/static/release-9-1-23.htmlhttps://www.postgresql.org/docs/current/static/release-9-2-18.htmlhttps://www.postgresql.org/docs/current/static/release-9-3-14.htmlhttps://www.postgresql.org/docs/current/static/release-9-4-9.htmlhttps://www.postgresql.org/docs/current/static/release-9-5-4.html
2016-12-09
Published