PostgreSQL pg_dump newline in object name executes arbitrary code in psql client and in restore target server
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 13.22, 14.19, 15.14 and 2 more.
Improper neutralization of newlines in pg_dump in PostgreSQL allows a user of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands inside a purpose-crafted object name. The same attacks can achieve SQL injection as a superuser of the restore target server. pg_dumpall, pg_restore, and pg_upgrade are also affected. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected. Versions before 11.20 are unaffected. CVE-2012-0868 had fixed this class of problem, but version 11.20 reintroduced it.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| >=11.20 <13.22, >=14 <14.19, >=15 <15.14, >=16 <16.10, >=17 <17.6 | 13.22, 14.19, 15.14, 16.10, 17.6 |
Exploit evidence
1 public sources
Vendor advisories
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket