First published: Mon May 06 2019(Updated: )
A vulnerability was found in postgresql versions 11.x prior to 11.3. The Windows installer for BigSQL-supplied PostgreSQL does not lock down the ACL of the binary installation directory or the ACL of the data directory; it keeps the inherited ACL. In the default configuration, an attacker having both an unprivileged Windows account and an unprivileged PostgreSQL account can cause the PostgreSQL service account to execute arbitrary code. An attacker having only the unprivileged Windows account can read arbitrary data directory files, essentially bypassing database-imposed read access limitations. An attacker having only the unprivileged Windows account can also delete certain data directory files.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
PostgreSQL PostgreSQL | <9.4.22 | |
PostgreSQL PostgreSQL | >=9.5.0<9.5.17 | |
PostgreSQL PostgreSQL | >=9.6.0<9.6.13 | |
PostgreSQL PostgreSQL | >=10.0<10.8 | |
PostgreSQL PostgreSQL | >=11.0<11.3 | |
Microsoft Windows |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID of this vulnerability is CVE-2019-10127.
The severity level of CVE-2019-10127 is high with a severity value of 8.8.
PostgreSQL versions 9.4.22, 9.5.0 to 9.5.17, 9.6.0 to 9.6.13, 10.0 to 10.8, and 11.0 to 11.3 are affected by CVE-2019-10127.
CVE-2019-10127 allows an attacker to execute arbitrary SQL commands with the permissions of the PostgreSQL service account.
To fix CVE-2019-10127, upgrade PostgreSQL to version 11.3 or later.