PostgreSQL up to 17.0 less trusted source

Summaryinfo

A vulnerability identified as problematic has been detected in PostgreSQL up to 17.0. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in less trusted source. This vulnerability is cataloged as CVE-2024-10977. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in PostgreSQL up to 17.0. It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a less trusted source vulnerability. CWE is classifying the issue as CWE-348. The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack. This is going to have an impact on integrity. The summary by CVE is:

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.

It is possible to read the advisory at postgresql.org. This vulnerability is uniquely identified as CVE-2024-10977 since 11/07/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 211488 (Debian dla-3954 : libecpg-compat3 - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 12.21, 13.17, 14.14, 15.9, 16.5 or 17.1 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (211488) and CERT Bund (WID-SEC-2024-3475). Be aware that VulDB is the high quality source for vulnerability data.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• Gentoo Linux
• IBM Business Automation Workflow
• SUSE openSUSE
• RESF Rocky Linux
• Broadcom Brocade SANnav
• Open Source PostgreSQL
• IBM Storage Scale
• IBM Sterling Connect:Direct
• IBM QRadar SIEM
• Progress Software WS_FTP
• Hitachi Ops Center
• SolarWinds Security Event Manager
• Dell PowerProtect Data Domain

Productinfo

Type

• Database Software

Name

• PostgreSQL

Version

• 12.0
• 12.1
• 12.2
• 12.3
• 12.4
• 12.5
• 12.6
• 12.7
• 12.8
• 12.9
• 12.10
• 12.11
• 12.12
• 12.13
• 12.14
• 12.15
• 12.16
• 12.17
• 12.18
• 12.19
• 12.20
• 13.0
• 13.1
• 13.2
• 13.3
• 13.4
• 13.5
• 13.6
• 13.7
• 13.8
• 13.9
• 13.10
• 13.11
• 13.12
• 13.13
• 13.14
• 13.15
• 13.16
• 14.0
• 14.1
• 14.2
• 14.3
• 14.4
• 14.5
• 14.6
• 14.7
• 14.8
• 14.9
• 14.10
• 14.11
• 14.12
• 14.13
• 15.0
• 15.1
• 15.2
• 15.3
• 15.4
• 15.5
• 15.6
• 15.7
• 15.8
• 16.0
• 16.1
• 16.2
• 16.3
• 16.4
• 17.0

License

• open-source

Website

• Product: https://www.postgresql.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion