Homepage

Incorrect Permission Assignment for Critical Resource Affecting postgresql14 package, versions <10.2-r0

Severity

 Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

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-ALPINE319-POSTGRESQL14-6110717
  • published8 Dec 2023
  • disclosed9 Feb 2018
Report a new vulnerability Found a mistake?

Introduced: 9 Feb 2018

CVE-2018-1053  (opens in a new tab)
CWE-732  (opens in a new tab)
CWE-377  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade Alpine:3.19 postgresql14 to version 10.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream postgresql14 package and not the postgresql14 package as distributed by Alpine. See How to fix? for Alpine:3.19 relevant fixed versions and status.

In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of pg_dumpall -g under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.