Stack memory corruption via undersized length variables
Published Mar 18, 2024 · Updated Nov 20, 2025
An out-of-bounds write in unixODBC's legacy PostgreSQL driver allows local users to corrupt stack memory on 64-bit systems. The driver passes three 32-bit length variables to ODBC routines that write 64-bit SQLLEN values, overwriting adjacent stack data. Exploitation requires use of this historical, unsupported example driver; upstream reports no evidence that distributions ship it.
Summary
What happened
An out-of-bounds write in unixODBC's legacy PostgreSQL driver allows local users to corrupt stack memory on 64-bit systems. The driver passes three 32-bit length variables to ODBC routines that write 64-bit SQLLEN values, overwriting adjacent stack data. Exploitation requires use of this historical, unsupported example driver; upstream reports no evidence that distributions ship it.
The record
- CVE
- CVE-2024-1013
- Published
- Mar 18, 2024
- Updated
- Nov 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-823
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo