Npgsql up to 8.0.2 NpgsqlConnector.FrontendMessages.cs WriteBind integer overflow

Summaryinfo

A vulnerability described as critical has been identified in Npgsql up to 8.0.2. This issue affects the function WriteBind of the file src/Npgsql/Internal/NpgsqlConnector.FrontendMessages.cs. Executing a manipulation can lead to integer overflow. The identification of this vulnerability is CVE-2024-32655. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as critical was found in Npgsql up to 8.0.2. This vulnerability affects the function WriteBind of the file src/Npgsql/Internal/NpgsqlConnector.FrontendMessages.cs. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Npgsql is the .NET data provider for PostgreSQL. In 8.0.2 and earlier, The `WriteBind()` method in `src/Npgsql/Internal/NpgsqlConnector.FrontendMessages.cs` uses `int` variables to store the message length and the sum of parameter lengths. Both variables overflow when the sum of parameter lengths becomes too large. This causes Npgsql to write a message size that is too small when constructing a Postgres protocol message to send it over the network to the database. When parsing the message, the database will only read a small number of bytes and treat any following bytes as new messages while they belong to the old message. Attackers can abuse this to inject arbitrary Postgres protocol messages into the connection, leading to the execution of arbitrary SQL statements on the application's behalf.

The advisory is available at github.com. This vulnerability was named CVE-2024-32655 since 04/16/2024. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 05/09/2024).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• Npgsql

Version

• 8.0.0
• 8.0.1
• 8.0.2

Website

• Product: https://github.com/npgsql/npgsql/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion