CVE-2024-27304

Workarounds

Reject user input large enough to cause a single query or bind message to exceed 4 GB in size.

SQL injection can occur if an attacker can cause a single query or bind message to exceed 4 GB in size. An integer overflow in the calculated message size can cause the one large message to be sent as multiple messages under the attacker's control.

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-27304 has a CVSS score of 9.8 (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 (4.18.2, 5.5.4); upgrading removes the vulnerable code path.

Kodem intelligence

The problem is resolved in v4.18.2 and v5.5.4.

1. What is CVE-2024-27304? CVE-2024-27304 is a high-severity SQL injection vulnerability in github.com/jackc/pgx (go), affecting versions < 4.18.2. It is fixed in 4.18.2, 5.5.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2024-27304? CVE-2024-27304 has a CVSS score of 9.8 (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.
3. Which packages are affected by CVE-2024-27304?
   • github.com/jackc/pgx (go) (versions < 4.18.2)
   • github.com/jackc/pgx/v4 (go) (versions < 4.18.2)
   • github.com/jackc/pgx/v5 (go) (versions >= 5.0.0, < 5.5.4)
4. Is there a fix for CVE-2024-27304? Yes. CVE-2024-27304 is fixed in 4.18.2, 5.5.4. Upgrade to this version or later.
5. Is CVE-2024-27304 exploitable, and should I be worried? Whether CVE-2024-27304 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
6. What actually determines whether CVE-2024-27304 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.
7. How do I fix CVE-2024-27304?
   • Upgrade github.com/jackc/pgx to 4.18.2 or later
   • Upgrade github.com/jackc/pgx to 5.5.4 or later
   • Upgrade github.com/jackc/pgx/v4 to 4.18.2 or later
   • Upgrade github.com/jackc/pgx/v5 to 5.5.4 or later