A vulnerability was found in postgresql versions 11.x prior to 11.3. The Windows installer for EnterpriseDB-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, this allows a local attacker to read arbitrary data directory files, essentially bypassing database-imposed read access limitations. In plausible non-default configurations, an attacker having both an unprivileged Windows account and an unprivileged PostgreSQL account can cause the PostgreSQL service account to execute arbitrary code.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Postgresql | Postgresql | * | 9.4.22 (excluding) |
| Postgresql | Postgresql | 9.5.0 (including) | 9.5.17 (excluding) |
| Postgresql | Postgresql | 9.6.0 (including) | 9.6.13 (excluding) |
| Postgresql | Postgresql | 10.0 (including) | 10.8 (excluding) |
| Postgresql | Postgresql | 11.0 (including) | 11.3 (excluding) |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: