What is CVE-2024-32655?

CVE-2024-32655 is a high-severity SQL injection vulnerability in Npgsql (nuget), affecting versions >= 8.0.0, < 8.0.3. It is fixed in 8.0.3, 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2024-32655?

CVE-2024-32655 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of Npgsql are affected by CVE-2024-32655?

Npgsql (nuget) versions >= 8.0.0, < 8.0.3 is affected.

Is there a fix for CVE-2024-32655?

Yes. CVE-2024-32655 is fixed in 8.0.3, 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7. Upgrade to this version or later.

Is CVE-2024-32655 exploitable, and should I be worried?

Whether CVE-2024-32655 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-32655 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-32655 in Npgsql

Q: How severe is CVE-2024-32655?

CVE-2024-32655 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of Npgsql are affected by CVE-2024-32655?

Npgsql (nuget) versions >= 8.0.0, < 8.0.3 is affected.

Q: Is there a fix for CVE-2024-32655?

Yes. CVE-2024-32655 is fixed in 8.0.3, 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7. Upgrade to this version or later.

Q: Is CVE-2024-32655 exploitable, and should I be worried?

Whether CVE-2024-32655 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-32655 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-32655?

Upgrade: Npgsql to 8.0.3 or later, Npgsql to 4.0.14 or later, Npgsql to 4.1.13 or later, Npgsql to 5.0.18 or later, Npgsql to 6.0.11 or later, Npgsql to 7.0.7 or later.

Summary

Npgsql vulnerable to SQL Injection via Protocol Message Size Overflow

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.

Impact

Attackers can issue arbitrary SQL statements to the database on behalf of the application. The final impact depends on the application that uses Npgsql, the data it stores in Postgres, etc.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2024-32655 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.0.3, 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7); upgrading removes the vulnerable code path.

Affected versions

Npgsql (>= 8.0.0, < 8.0.3) Npgsql (<= 4.0.13) Npgsql (>= 4.1.0, < 4.1.13) Npgsql (>= 5.0.0, < 5.0.18) Npgsql (>= 6.0.0, < 6.0.11) Npgsql (>= 7.0.0, < 7.0.7)

Security releases

Npgsql → 8.0.3 (nuget) Npgsql → 4.0.14 (nuget) Npgsql → 4.1.13 (nuget) Npgsql → 5.0.18 (nuget) Npgsql → 6.0.11 (nuget) Npgsql → 7.0.7 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

Npgsql to 8.0.3 or later; Npgsql to 4.0.14 or later; Npgsql to 4.1.13 or later; Npgsql to 5.0.18 or later; Npgsql to 6.0.11 or later; Npgsql to 7.0.7 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-32655? CVE-2024-32655 is a high-severity SQL injection vulnerability in Npgsql (nuget), affecting versions >= 8.0.0, < 8.0.3. It is fixed in 8.0.3, 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2024-32655? CVE-2024-32655 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of Npgsql are affected by CVE-2024-32655? Npgsql (nuget) versions >= 8.0.0, < 8.0.3 is affected.
Is there a fix for CVE-2024-32655? Yes. CVE-2024-32655 is fixed in 8.0.3, 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7. Upgrade to this version or later.
Is CVE-2024-32655 exploitable, and should I be worried? Whether CVE-2024-32655 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-32655 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-32655?
- Upgrade Npgsql to 8.0.3 or later
- Upgrade Npgsql to 4.0.14 or later
- Upgrade Npgsql to 4.1.13 or later
- Upgrade Npgsql to 5.0.18 or later
- Upgrade Npgsql to 6.0.11 or later
- Upgrade Npgsql to 7.0.7 or later