Homepage

Link Following Affecting postgresql-upgrade package, versions <0:9.2.23-3.el7_4

Severity

 Recommended
0.0
medium
0
10

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.06% (29th percentile)

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-ORACLE7-POSTGRESQLUPGRADE-2520545
  • published10 Apr 2022
  • disclosed22 Nov 2017
Report a new vulnerability Found a mistake?

Introduced: 22 Nov 2017

CVE-2017-12172  (opens in a new tab)
CWE-59  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade Oracle:7 postgresql-upgrade to version 0:9.2.23-3.el7_4 or higher.
This issue was patched in ELSA-2017-3402.

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 Oracle. See How to fix? for Oracle: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.