Skip to content
NewA calmer, faster ZeroHour

unixODBC <=2.3.14 Multiple Heap Buffer Overflows

Original title: unixODBC <=2.3.14 Multiple Heap Buffer Overflows, Underflows, and Over-Reads

Full Disclosure ()1 · 1 read
Part of a story covered by 3 sourcesunixODBC <=2.3.14 Heap Overflows, Races, and Truncation FlawsMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Heap buffer overflows, underflows, and over-reads in unixODBC can corrupt shared heap state across connections and cause denial of service.

unixODBC versions 2.3.14 and below contain multiple heap buffer overflows, underflows, and over-reads. Attackers who can influence various arguments passed thereto can trigger the heap-based buffer overflows inside of the unixODBC driver manager itself, potentially corrupting the shared heap state across connections, crash the driver manager (thereby causing denial of service conditions, multi-tenant data loss, and such related issues.

Key facts
  • Heap buffer overflows inside unixODBC driver manager
  • Corruption of shared heap state across connections
  • Denial of service conditions
  • Multi-tenant data loss
Security assessment · AI, from the article

Impact: heap buffer overflows that corrupt shared heap state and cause DoS

Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

Posted by Daniel Owens via Fulldisclosure on Nov 04 unixODBC versions 2. 3. 14 and below contain multiple heap buffer overflows, underflows, and over-reads.

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.