Описание
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.
A flaw was found in PostgreSQL's error message handling. This vulnerability allows a Man-in-the-middle attacker to inject arbitrary non-NUL bytes into the libpq application via a server error message.
Отчет
This vulnerability affects PostgreSQL clients that handle error messages from untrusted servers, which may cause error messages to be misinterpreted as valid query results.
Меры по смягчению последствий
Make sure PostgreSQL is configured to use trusted SSL or GSS settings to prevent untrusted servers from sending error messages. Additionally, when interpreting output from the psql command line interface, make sure to distinguish between error messages and valid data.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 7 | postgresql | Out of support scope | ||
| Red Hat Enterprise Linux 8 | postgresql:12/postgresql | Fix deferred | ||
| Red Hat Enterprise Linux 8 | postgresql:13/postgresql | Fix deferred | ||
| Red Hat Enterprise Linux 8 | postgresql:15/postgresql | Fix deferred | ||
| Red Hat Enterprise Linux 8 | postgresql:16/postgresql | Fix deferred | ||
| Red Hat Enterprise Linux 9 | postgresql | Fix deferred | ||
| Red Hat Enterprise Linux 9 | postgresql:15/postgresql | Fix deferred | ||
| Red Hat Enterprise Linux 9 | postgresql:16/postgresql | Fix deferred |
Показывать по
Дополнительная информация
Статус:
3.1 Low
CVSS3
Связанные уязвимости
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.
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.
Client use of server error message in PostgreSQL allows a server not t ...
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.
3.1 Low
CVSS3