Due to both the EnterpriseDB and BigSQL Windows installers not locking down the permissions of the PostgreSQL binary installation directory and the data directory, an unprivileged Windows user account and an unprivileged PostgreSQL account could cause the PostgreSQL service account to execute arbitrary code.
This vulnerability is present in all supported versions of PostgreSQL for these installers, and possibly exists in older versions. Both sets of installers have fixed the permissions for these directories for both new and existing installations. If you have installed PostgreSQL on Windows using other methods, we advise that you check that your PostgreSQL binary directories are writable only to trusted users and that your data directories are only accessible to trusted users.
The PostgreSQL project thanks Conner Jones for reporting this problem.
| Affected Version | Fixed In | Fix Published |
|---|---|---|
| 11 | 11.3 | May 9, 2019 |
| 10 | 10.8 | May 9, 2019 |
| 9.6 | 9.6.13 | May 9, 2019 |
| 9.5 | 9.5.17 | May 9, 2019 |
| 9.4 | 9.4.22 | May 9, 2019 |
For more information about PostgreSQL versioning, please visit the versioning page.
| Overall Score | 7.0 |
|---|---|
| Component | packaging |
| Vector | AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
If you wish to report a new security vulnerability in PostgreSQL, please send an email to security@postgresql.org.
For reporting non-security bugs, please see the Report a Bug page.