CVE-2024-27289

Workarounds

Do not use the simple protocol or do not place a minus directly before a placeholder.

SQL injection can occur when all of the following conditions are met:

1. The non-default simple protocol is used.
2. A placeholder for a numeric value must be immediately preceded by a minus.
3. There must be a second placeholder for a string value after the first placeholder; both
   must be on the same line.
4. Both parameter values must be user-controlled.

e.g.

Simple mode must be enabled:

// connection string includes "prefer_simple_protocol=true"
// or
// directly enabled in code
config.ConnConfig.PreferSimpleProtocol = true

Parameterized query:

SELECT * FROM example WHERE result=-$1 OR name=$2;

Parameter values:

$1 => -42
$2 => "foo\n 1 AND 1=0 UNION SELECT * FROM secrets; --"

Resulting query after preparation:

SELECT * FROM example WHERE result=--42 OR name= 'foo
1 AND 1=0 UNION SELECT * FROM secrets; --';

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-27289 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 (4.18.2); upgrading removes the vulnerable code path.

Kodem intelligence

The problem is resolved in v4.18.2.

1. What is CVE-2024-27289? CVE-2024-27289 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. 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-27289? CVE-2024-27289 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.
3. Which packages are affected by CVE-2024-27289?
   • github.com/jackc/pgx (go) (versions < 4.18.2)
   • github.com/jackc/pgx/v4 (go) (versions < 4.18.2)
4. Is there a fix for CVE-2024-27289? Yes. CVE-2024-27289 is fixed in 4.18.2. Upgrade to this version or later.
5. Is CVE-2024-27289 exploitable, and should I be worried? Whether CVE-2024-27289 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-27289 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-27289?
   • Upgrade github.com/jackc/pgx to 4.18.2 or later
   • Upgrade github.com/jackc/pgx/v4 to 4.18.2 or later

Other vulnerabilities in github.com/jackc/pgx