First published: Mon Nov 13 2017(Updated: )
Last updated 24 July 2024
Credit: security@debian.org security@debian.org security@debian.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/postgresql-common | 225+deb11u1 248 262 263 | |
PostgreSQL | ||
PostgreSQL | ||
Ubuntu | =14.04 | |
Ubuntu | =16.04 | |
Ubuntu | =17.04 | |
Ubuntu | =17.10 | |
Debian | =8.0 | |
Debian | =9.0 | |
All of | ||
PostgreSQL Client | ||
Any of | ||
Ubuntu Linux | =14.04 | |
Ubuntu Linux | =16.04 | |
Ubuntu Linux | =17.04 | |
Ubuntu Linux | =17.10 | |
Debian | =8.0 | |
Debian | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-8806 is considered to have a moderate severity level due to its potential impact on the security of PostgreSQL installations in Debian and Ubuntu.
To fix CVE-2017-8806, you should upgrade the postgresql-common package to version 181+deb9u1 or later.
CVE-2017-8806 affects Debian and Ubuntu systems that use PostgreSQL with vulnerable versions of the postgresql-common package.
A workaround for CVE-2017-8806 includes ensuring that symbolic links are handled securely in your PostgreSQL configuration.
CVE-2017-8806 impacts installations of PostgreSQL that rely on Debian's postgresql-common scripts for managing clusters.