CVE-2017-12172: High severity postgresql common vulnerability
PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, 9.5.x before 9.5.10, 9.4.x before 9.4.15, 9.3.x before 9.3.20, and 9.2.x before 9.2.24 runs under a non-root operating system account, and database superusers have effective ability to run arbitrary code under that system account. PostgreSQL provides a script for starting the database server during system boot. Packages of PostgreSQL for many operating systems provide their own, packager-authored startup implementations. Several implementations use a log file name that the database superuser can replace with a symbolic link. As root, they open(), chmod() and/or chown() this log file name. This often suffices for the database superuser to escalate to root privileges when root starts the server.
Other sources
PostgreSQL runs under a non-root operating system account, and database superusers have effective ability to run arbitrary code under that system account. PostgreSQL provides a script for starting the database server during system boot. Packages of PostgreSQL for many operating systems provide their own, packager-authored startup implementations. Several implementations use a log file name that the database superuser can replace with a symbolic link. As root, the scripts redirect stdout and stderr content to the log file name. This often suffices for the database superuser to escalate to root privileges when root starts the server.
Supported, Vulnerable Versions: 9.2 - 10
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-12172?
CVE-2017-12172 has a high severity rating as it allows database superusers to execute arbitrary code.
How do I fix CVE-2017-12172?
To fix CVE-2017-12172, upgrade PostgreSQL to version 10.1 or later, 9.6.6 or later, 9.5.10 or later, 9.4.15 or later, 9.3.20 or later, or 9.2.24 or later.
What versions of PostgreSQL are affected by CVE-2017-12172?
CVE-2017-12172 affects PostgreSQL versions up to 10.0, 9.6.5, 9.5.9, 9.4.14, 9.3.19, and 9.2.23.
What causes the vulnerability in CVE-2017-12172?
The vulnerability in CVE-2017-12172 is caused by PostgreSQL running under a non-root operating system account, allowing superusers to exploit it.
Is there a workaround for CVE-2017-12172 if I cannot upgrade?
Currently, there isn't a recommended workaround for CVE-2017-12172 except to upgrade to a patched version of PostgreSQL.