Link Following Affecting postgresql-upgrade package, versions <0:9.2.23-3.el7_4
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS7-POSTGRESQLUPGRADE-2095337
- published26 Jul 2021
- disclosed9 Nov 2017
Introduced: 9 Nov 2017
CVE-2017-12172 (opens in a new tab)How to fix?
Upgrade Centos:7 postgresql-upgrade to version 0:9.2.23-3.el7_4 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql-upgrade package and not the postgresql-upgrade package as distributed by Centos.
See How to fix? for Centos:7 relevant fixed versions and status.
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.