SQL injection via the :comment option in Postgrex.stream/4
A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 0.22.4 and *.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in elixir-ecto postgrex allows SQL Injection via the :comment option of Postgrex.stream/4. An attacker who can influence that value can close the comment delimiter with */ and extend the streamed statement with their own clauses, which execute under the connection's role. Ecto exposes the same option through Ecto.Repo.stream/2. Postgrex appends the comment by concatenating it into the statement text sent in the Parse message, without escaping or rejecting */. The option is validated by comment_not_present!/1 at every other execution point; stream/4 never calls it. Because Parse accepts a single command, the injection is confined to the streamed statement and further statements cannot be chained. This issue affects postgrex: from 0.19.3 before 0.22.4.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| elixir-ecto | postgrex | >=0.19.3 <0.22.4 | 0.22.4 |
| elixir-ecto | =4971a2722fa72f8e1b54a2c403cad4c43916e36d, >=0.19.3 <0.22.4 | *, 0.22.4 |
Exploit evidence
1 public sources
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket