Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

npgsql

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.1NuGetPublished

    Npgsql vulnerable to SQL Injection via Protocol Message Size Overflow

    CVE-2024-32655 · GHSA-x9vc-6hfv-hg8c

    Affected
    • NuGet npgsql >= 8.0.0, < 8.0.3; <= 4.0.13; >= 4.1.0, < 4.1.13; >= 5.0.0, < 5.0.18; >= 6.0.0, < 6.0.11; >= 7.0.0, < 7.0.7
    Fixed in
    4.0.148.0.36.0.117.0.75.0.184.1.13· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 8.0.3, 7.0.7, 6.0.11 or 3 more by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →