CVE-2024-10977 Affecting postgresql17-pltcl package, versions <17.2-150600.13.5.1


Severity

Recommended
0.0
low
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES156-POSTGRESQL17PLTCL-8441823
  • published27 Nov 2024
  • disclosed26 Nov 2024

Introduced: 26 Nov 2024

NewCVE-2024-10977  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 postgresql17-pltcl to version 17.2-150600.13.5.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream postgresql17-pltcl package and not the postgresql17-pltcl package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

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.

CVSS Scores

version 3.1