Npgsql Vulnerable to SQL Injection via Protocol Message Size Overflow
npgsql
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Npgsql NuGet |
|
|
npgsql
| Product | Affected | Fixed in |
|---|---|---|
| Npgsql NuGet |
|
|
4.1.135.0.186.0.117.0.7Npgsql is the .NET data provider for PostgreSQL. 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. This vulnerability is fixed in 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7, and 8.0.3.
From the CVE record · GitHub_M
Npgsql's WriteBind() can overflow when the combined length of parameters becomes too large, causing it to send an incorrect message size to the database. An attacker who can trigger this condition can inject PostgreSQL protocol messages and execute arbitrary SQL on the application's behalf; the input does not specify authentication or user-interaction requirements.
Check applications using NuGet Npgsql versions earlier than 4.0.14, 4.1.0–4.1.12, 5.0.0–5.0.17, 6.0.0–6.0.10, 7.0.0–7.0.6, or 8.0.0–8.0.2.