First published: Wed Feb 17 2016(Updated: )
PostgreSQL before 9.1.20, 9.2.x before 9.2.15, 9.3.x before 9.3.11, 9.4.x before 9.4.6, and 9.5.x before 9.5.1 does not properly restrict access to unspecified custom configuration settings (GUCS) for PL/Java, which allows attackers to gain privileges via unspecified vectors.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
PostgreSQL Client | >=9.1.0<9.1.20 | |
PostgreSQL Client | >=9.2<9.2.15 | |
PostgreSQL Client | >=9.3<9.3.11 | |
PostgreSQL Client | >=9.4<9.4.6 | |
PostgreSQL Client | =9.5 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =15.10 | |
Debian | =7.0 | |
Debian | =8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-0766 is considered a medium severity vulnerability as it allows attackers to gain elevated privileges.
To fix CVE-2016-0766, you should upgrade PostgreSQL to a version above 9.1.20, 9.2.15, 9.3.11, 9.4.6, or 9.5.1.
Affected PostgreSQL versions include versions prior to 9.1.20, 9.2.x before 9.2.15, 9.3.x before 9.3.11, 9.4.x before 9.4.6, and 9.5.x before 9.5.1.
Yes, CVE-2016-0766 can potentially be exploited remotely if proper network security measures are not in place.
CVE-2016-0766 affects systems running specific versions of PostgreSQL and some Linux distributions like Ubuntu and Debian.