Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application. For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results. This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.
The PostgreSQL project thanks Jacob Champion for reporting this problem.
| Affected Version | Fixed In | Fix Published |
|---|---|---|
| 17 | 17.1 | Nov. 14, 2024 |
| 16 | 16.5 | Nov. 14, 2024 |
| 15 | 15.9 | Nov. 14, 2024 |
| 14 | 14.14 | Nov. 14, 2024 |
| 13 | 13.17 | Nov. 14, 2024 |
| 12 | 12.21 | Nov. 14, 2024 |
For more information about PostgreSQL versioning, please visit the versioning page.
| Overall Score | 3.1 |
|---|---|
| Component | client |
| Vector | AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N |
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.