Vulnerabilities · 2017 · Postgresql
CVE-2017-12172
Postgresql 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.
Affected products
Postgresql. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Postgresql runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.postgresql.org/about/news/1801/ · Vendor Advisory
- www.postgresql.org/support/security/ · Vendor Advisory
- www.securityfocus.com/bid/101949 · Third Party Advisory
- www.securitytracker.com/id/1039752 · Third Party Advisory
- access.redhat.com/errata/RHSA-2017:3402 · Third Party Advisory
- access.redhat.com/errata/RHSA-2017:3403 · Third Party Advisory
- access.redhat.com/errata/RHSA-2017:3404 · Third Party Advisory
- access.redhat.com/errata/RHSA-2017:3405 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2017-12172
- cve.org/CVERecord?id=CVE-2017-12172
More vulnerabilities in Postgresql products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.