First published: Mon Jan 29 2018(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/postgresql-10 | ||
debian/postgresql-9.1 | ||
ubuntu/postgresql-10 | <10.2-1 | 10.2-1 |
ubuntu/postgresql-9.3 | <9.3.21-0ubuntu0.14.0 | 9.3.21-0ubuntu0.14.0 |
ubuntu/postgresql-9.5 | <9.5.11-0ubuntu0.16.04 | 9.5.11-0ubuntu0.16.04 |
ubuntu/postgresql-9.6 | <9.6.7-0ubuntu0.17.10 | 9.6.7-0ubuntu0.17.10 |
redhat/postgresql | <9.3.21 | 9.3.21 |
redhat/postgresql | <9.4.16 | 9.4.16 |
redhat/postgresql | <9.5.11 | 9.5.11 |
redhat/postgresql | <9.6.7 | 9.6.7 |
redhat/postgresql | <10.2 | 10.2 |
PostgreSQL PostgreSQL | >=9.3.0<9.3.21 | |
PostgreSQL PostgreSQL | >=9.4.0<9.4.16 | |
PostgreSQL PostgreSQL | >=9.5.0<9.5.11 | |
PostgreSQL PostgreSQL | >=9.6.0<9.6.7 | |
PostgreSQL PostgreSQL | =10.0 | |
PostgreSQL PostgreSQL | =10.1 | |
Debian Debian Linux | =7.0 | |
Canonical Ubuntu Linux | =14.04 | |
Canonical Ubuntu Linux | =16.04 | |
Canonical Ubuntu Linux | =17.10 | |
Redhat Cloudforms | =4.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2018-1053.
CVE-2018-1053 has a severity level of high.
The affected software includes PostgreSQL versions 9.3.x, 9.4.x, 9.5.x, 9.6.x, and 10.x.
To fix CVE-2018-1053, upgrade to PostgreSQL versions 9.3.21, 9.4.16, 9.5.11, 9.6.7, or 10.2.
Yes, you can find additional references for CVE-2018-1053 at the following links: [link1], [link2], [link3].