PostgreSQL psqlODBC
psqlODBC does not validate column numbers and row indexes in binding and descriptor functions
Several psqlODBC entry points use an application-supplied column number or row index as an array index without validating it. SQLBindCol with a column number above 32767 wraps the binding count negative and a later copy runs off the array. A negative SQL_DESC_COUNT on an application row descriptor unbinds columns at negative indexes. SQLColAttribute with a very large column number uses a negative index. SQLSetPos(SQL_ADD) does not check the row number against the rowset size. An application that forwards untrusted column or row numbers exposes its process to out-of-bounds reads and writes. Versions before psqlODBC 18.00.0006 are affected.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 18.00.0006
Fixed in 18.00.0006
Mitigation
Upgrade to psqlODBC 18.00.0006 or later. SQLBindCol rejects column numbers above 32767 with SQLSTATE 07009, a negative descriptor count is ignored, and the column and row indexes are range-checked.
Workaround
Validate column numbers (1..32767 and within the result set) and row numbers (within the rowset) in the application before calling the driver.
References
- Vendor advisory github.com/postgresql-interfaces/psqlodbc/secu…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.