unixODBC <=2.3.14 Heap Overflows, Races, and Truncation Flaws
First merged summary.
unixODBC versions 2.3.14 and below have heap buffer overflows, data races, and truncation issues that can cause memory corruption and crashes.
unixODBC versions 2.3.14 and below contain multiple issues in the driver manager. Heap buffer overflows, underflows, and over-reads can corrupt shared heap state across connections and lead to denial of service. Data races in connection-pooling state and races between teardown and error-handling can cause double-frees and use-after-frees. Truncation of 64-bit SQLLEN buffer_length to 32-bit int without validation enables out-of-bounds memcpy and potential memory corruption. These flaws affect multi-tenant environments and may result in crashes or data loss.
- Heap buffer overflows, underflows, over-reads in unixODBC driver manager
- Corruption of shared heap state across connections
- Data races in connection-pooling state data
- Race between teardown and error-handling
- Double-frees and use-after-frees possible
- Truncation of SQLLEN to 32-bit int causes OOB writes
What each outlet adds
beyond the shared facts- Full DisclosureThree vulnerabilities including buffer overflows, races, and truncation in unixODBC <=2.3.14
- Vendors
- unixODBC
Coverage
oldest first · one row per article · UTCunixODBC <=2.3.14 Multiple Heap Buffer Overflows
Heap buffer overflows, underflows, and over-reads in unixODBC can corrupt shared heap state across connections and cause denial of service.
unixODBC <=2.3.14 Multiple Races
Data races in connection-pooling state data and races between teardown and error-handling can cause double-frees and use-after-frees.
unixODBC <=2.3.14 vulnerable to rude truncation causing out-of-bounds memcpy
Rude truncation of 64-bit SQLLEN buffer_length to 32-bit int in unixODBC <=2.3.14 enables potential out-of-bounds memory writes.