| Package | Affected versions | Patched versions |
|---|---|---|
| org.postgresql:postgresql | ≥ 42.3.0, < 42.3.9≥ 42.4.0, < 42.4.4≥ 42.5.0, < 42.5.5≥ 42.6.0, < 42.6.1≥ 42.7.0, < 42.7.2< 42.2.28 | 42.3.942.4.442.5.542.6.142.7.242.2.28 |
| postgresql jdbc driver | ≥ 42.3.0, < 42.3.9≥ 42.4.0, < 42.4.4≥ 42.5.0, < 42.5.5≥ 42.6.0, < 42.6.1≥ 42.7.0, < 42.7.2< 42.2.28 | 42.3.942.4.442.5.542.6.142.7.242.2.28 |
SQL injection is possible when using the non-default connection property preferQueryMode=simple in combination with application code that has a vulnerable SQL that negates a parameter value.
There is no vulnerability in the driver when using the default query mode. Users that do not override the query mode are not impacted.
To exploit this behavior the following conditions must be met:
-)The prior behavior of the driver when operating in simple query mode would inline the negative value of the first parameter and cause the resulting line to be treated as a -- SQL comment. That would extend to the beginning of the next parameter and cause the quoting of that parameter to be consumed by the comment line. If that string parameter includes a newline, the resulting text would appear unescaped in the resulting SQL.
When operating in the default extended query mode this would not be an issue as the parameter values are sent separately to the server. Only in simple query mode the parameter values are inlined into the executed SQL causing this issue.
PreparedStatement stmt = conn.prepareStatement("SELECT -?, ?");
stmt.setInt(1, -1);
stmt.setString(2, "\nWHERE false --");
ResultSet rs = stmt.executeQuery();
The resulting SQL when operating in simple query mode would be:
SELECT --1,'
WHERE false --'
The contents of the second parameter get injected into the command. Note how both the number of result columns and the WHERE clause of the command have changed. A more elaborate example could execute arbitrary other SQL commands.
Problem will be patched upgrade to 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9, 42.2.28, 42.2.28.jre7
The patch fixes the inlining of parameters by forcing them all to be serialized as wrapped literals. The SQL in the prior example would be transformed into:
SELECT -('-1'::int4), ('
WHERE false --')
Do not use the connection propertypreferQueryMode=simple. (NOTE: If you do not explicitly specify a query mode then you are using the default of extended and are not impacted by this issue.)
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free