MGASA-2018-0137

See a problem?
Please try reporting it to the source first.
Source
https://advisories.mageia.org/MGASA-2018-0137.html
Import Source
https://advisories.mageia.org/MGASA-2018-0137.json
JSON Data
https://api.test.osv.dev/v1/vulns/MGASA-2018-0137
Related
Published
2018-02-24T23:25:24Z
Modified
2018-02-24T22:52:21Z
Summary
Updated postgresql packages fix security vulnerability
Details

In postgresql 9.4.x before 9.4.16 and 9.6.x before 9.6.7, pgupgrade creates file in current working directory containing the output of pg_dumpall -g under umask which was in effect when the user invoked pgupgrade, 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 (CVE-2018-1053).

Note that on Mageia 5, only the postgresql9.4 update is being provided. Users of the postgresql9.3 package should migrate to 9.4.

References
Credits

Affected packages

Mageia:5 / postgresql9.4

Package

Name
postgresql9.4
Purl
pkg:rpm/mageia/postgresql9.4?distro=mageia-5

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
9.4.16-1.mga5

Ecosystem specific 

{
    "section": "core"
}

Mageia:6 / postgresql9.4

Package

Name
postgresql9.4
Purl
pkg:rpm/mageia/postgresql9.4?distro=mageia-6

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
9.4.16-1.mga6

Ecosystem specific 

{
    "section": "core"
}

Mageia:6 / postgresql9.6

Package

Name
postgresql9.6
Purl
pkg:rpm/mageia/postgresql9.6?distro=mageia-6

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
9.6.7-1.mga6

Ecosystem specific 

{
    "section": "core"
}