Ubuntu Security Notice USN-3564-1
9th February, 2018
postgresql-9.3, postgresql-9.5, postgresql-9.6 vulnerability
A security issue affects these releases of Ubuntu and its derivatives:
PostgreSQL could be made to expose sensitive information.
Software description
It was discovered that PostgreSQL incorrectly handled certain temp files.
An attacker could possibly use this to access sensitive information.
Update instructions
The problem can be corrected by updating your system to the following package version:
Ubuntu 17.10:
postgresql-9.6 9.6.7-0ubuntu0.17.10
Ubuntu 16.04 LTS:
postgresql-9.5 9.5.11-0ubuntu0.16.04
Ubuntu 14.04 LTS:
postgresql-9.3 9.3.21-0ubuntu0.14.04
To update your system, please follow these instructions: https://wiki.ubuntu.com/Security/Upgrades.
This update uses a new upstream release, which includes additional bug
fixes. After a standard system update you need to restart PostgreSQL to
make all the necessary changes.
References
CVE-2018-1053
Continue reading...
9th February, 2018
postgresql-9.3, postgresql-9.5, postgresql-9.6 vulnerability
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 17.10
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
PostgreSQL could be made to expose sensitive information.
Software description
- postgresql-9.3 - Object-relational SQL database
- postgresql-9.5 - Object-relational SQL database
- postgresql-9.6 - Object-relational SQL database
It was discovered that PostgreSQL incorrectly handled certain temp files.
An attacker could possibly use this to access sensitive information.
Update instructions
The problem can be corrected by updating your system to the following package version:
Ubuntu 17.10:
postgresql-9.6 9.6.7-0ubuntu0.17.10
Ubuntu 16.04 LTS:
postgresql-9.5 9.5.11-0ubuntu0.16.04
Ubuntu 14.04 LTS:
postgresql-9.3 9.3.21-0ubuntu0.14.04
To update your system, please follow these instructions: https://wiki.ubuntu.com/Security/Upgrades.
This update uses a new upstream release, which includes additional bug
fixes. After a standard system update you need to restart PostgreSQL to
make all the necessary changes.
References
CVE-2018-1053
Continue reading...