# CVE-2024-32655: Npgsql Vulnerable to SQL Injection via Protocol Message Size Overflow

> Attackers can inject arbitrary SQL statements by exploiting an integer overflow in Npgsql's protocol message construction, affecting .NET applications using PostgreSQL.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2024
- **Updated:** 12 Dec 2024
- **Also known as:** GHSA-x9vc-6hfv-hg8c, UBUNTU-CVE-2024-32655

## What is CVE-2024-32655?

CVE-2024-32655 is a high-severity SQL injection vulnerability in npgsql, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Npgsql 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2024-32655?

12 open source packages ship an affected version, including Npgsql.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Npgsql` | NuGet | All versions | 4.0.14 |
| `Npgsql` | NuGet | All versions | 4.0.14 |
| `Npgsql` | NuGet | From 4.1.0 | 4.1.13 |
| `Npgsql` | NuGet | From 4.1.0 | 4.1.13 |
| `Npgsql` | NuGet | From 5.0.0 | 5.0.18 |
| `Npgsql` | NuGet | From 5.0.0 | 5.0.18 |
| `Npgsql` | NuGet | From 6.0.0 | 6.0.11 |
| `Npgsql` | NuGet | From 6.0.0 | 6.0.11 |
| `Npgsql` | NuGet | From 7.0.0 | 7.0.7 |
| `Npgsql` | NuGet | From 7.0.0 | 7.0.7 |
| `Npgsql` | NuGet | From 8.0.0 | 8.0.3 |
| `Npgsql` | NuGet | From 8.0.0 | 8.0.3 |

## How do I fix CVE-2024-32655?

Upgrade Npgsql to a fixed version for your release line: 4.0.14, 4.1.13, 5.0.18 or 6.0.11.

## Is CVE-2024-32655 being exploited?

There is no known exploitation of CVE-2024-32655 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32655 and fix it if it is affected.

What it is: CVE-2024-32655 is a high-severity SQL injection vulnerability in npgsql, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32655 in the wild and no public exploit code.

Affected packages and fixed versions:
- Npgsql (NuGet): affected all versions; fixed in 4.0.14
- Npgsql (NuGet): affected all versions; fixed in 4.0.14
- Npgsql (NuGet): affected from 4.1.0; fixed in 4.1.13
- Npgsql (NuGet): affected from 4.1.0; fixed in 4.1.13
- Npgsql (NuGet): affected from 5.0.0; fixed in 5.0.18
- Npgsql (NuGet): affected from 5.0.0; fixed in 5.0.18
- Npgsql (NuGet): affected from 6.0.0; fixed in 6.0.11
- Npgsql (NuGet): affected from 6.0.0; fixed in 6.0.11
- Npgsql (NuGet): affected from 7.0.0; fixed in 7.0.7
- Npgsql (NuGet): affected from 7.0.0; fixed in 7.0.7
- Npgsql (NuGet): affected from 8.0.0; fixed in 8.0.3
- Npgsql (NuGet): affected from 8.0.0; fixed in 8.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-32655/ (Markdown: https://insights.sbomify.com/CVE-2024-32655/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32655
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32655
- OSV: https://osv.dev/vulnerability/CVE-2024-32655

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32655/
Summaries are generated and may contain mistakes; the official description above is the record.