An out-of-bounds stack write flaw was found in unixODBC on 64-bit architectures where the caller has 4 bytes and callee writes 8 bytes. This issue may go unnoticed on little-endian architectures, while big-endian architectures can be broken.
CVE-2024-1013
This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
March 18, 2024
Last Modified
March 26, 2025
References (6)
- secalert@redhathttps://access.redhat.com/security/cve/CVE-2024-1013
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=2260823
- secalert@redhathttps://github.com/lurcher/unixODBC/pull/157
- af854a3a-2127-422b-91ae-364da2661108https://access.redhat.com/security/cve/CVE-2024-1013
- af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=2260823
- af854a3a-2127-422b-91ae-364da2661108https://github.com/lurcher/unixODBC/pull/157
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | unixodbc-dev (2.3.9-5ubuntu0.1) @ jammy | 2026-05-24 | ubuntu |
| ubuntu | unixodbc-dev (2.3.12-1ubuntu0.24.04.1) @ noble | 2026-05-24 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| unixodbc | 2.3.11-1 ... 2.3.9-5 (14 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| unixodbc | 2.3.11-2 ... 2.3.14-2 (8 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| unixodbc | 2.3.12-2, 2.3.12-2+deb13u1, 2.3.14-1, 2.3.14-2 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| unixodbc | 2.3.12-2 | 2.3.14-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(3)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 5× in last 7d / 33× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 142 total refreshes for this CVE.
- 2026-08-25 13:47 UTCEPSS rescore
- 2026-08-23 00:17 UTCEPSS rescore
- 2026-08-21 23:47 UTCEPSS rescore
- 2026-08-20 22:53 UTCEPSS rescore
- 2026-08-19 17:02 UTCEPSS rescore
- 2026-08-18 13:46 UTCEPSS rescore
- 2026-08-17 13:45 UTCEPSS rescore
- 2026-08-16 16:18 UTCOSV refresh
- 2026-08-16 14:54 UTCEPSS rescore
- 2026-08-16 02:12 UTCEPSS rescore
- 2026-08-15 01:28 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-12 13:49 UTCEPSS rescore
- 2026-08-11 13:40 UTCEPSS rescore
- 2026-08-10 23:58 UTCEPSS rescore
- 2026-08-09 13:45 UTCEPSS rescore
- 2026-08-09 13:45 UTCEPSS rescore
- 2026-08-08 16:35 UTCEPSS rescore
- 2026-08-07 16:25 UTCEPSS rescore
- 2026-08-06 13:45 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-04 15:08 UTCEPSS rescore
- 2026-08-04 10:36 UTCEPSS rescore
- 2026-08-03 10:34 UTCEPSS rescore
- 2026-08-02 02:25 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-02 02:25 UTCEPSS rescore
- 2026-08-01 10:06 UTCOSV refresh
- 2026-08-01 04:14 UTCEPSS rescore
- 2026-08-01 04:14 UTCEPSS rescore
- 2026-07-30 16:26 UTCEPSS rescore
- 2026-07-30 01:29 UTCEPSS rescore
- 2026-07-28 15:34 UTCEPSS rescore
- 2026-07-27 14:11 UTCEPSS rescore
- 2026-07-26 14:53 UTCEPSS rescore
- 2026-07-26 14:53 UTCEPSS rescore
- 2026-07-25 14:16 UTCEPSS rescore
- 2026-07-24 14:16 UTCEPSS rescore
- 2026-07-23 14:17 UTCEPSS rescore
- 2026-07-23 14:17 UTCEPSS rescore
- 2026-07-23 02:31 UTCEG score recompute
- 2026-07-22 23:17 UTCEG score recompute▲ 0.70
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-20 17:06 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-14 16:55 UTCOSV refresh
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-08 15:13 UTCEPSS rescore
- 2026-07-07 13:45 UTCEPSS rescore
- 2026-07-07 13:45 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-05 02:29 UTCEPSS rescore
- 2026-07-04 06:30 UTCEPSS rescore
- 2026-07-04 06:30 UTCEPSS rescore
- 2026-07-01 15:05 UTCEPSS rescore
- 2026-06-30 23:21 UTCEPSS rescore
- 2026-06-30 23:21 UTCEPSS rescore
- 2026-06-29 14:05 UTCEPSS rescore
- 2026-06-28 14:06 UTCEPSS rescore
- 2026-06-28 14:06 UTCEPSS rescore
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-27 03:07 UTCEPSS rescore
- 2026-06-27 03:07 UTCEPSS rescore
- 2026-06-26 17:39 UTCOSV refresh
- 2026-06-25 13:48 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-23 21:32 UTCEPSS rescore
- 2026-06-23 21:31 UTCEPSS rescore
- 2026-06-22 14:24 UTCEPSS rescore
- 2026-06-22 14:24 UTCEPSS rescore
- 2026-06-21 14:55 UTCEPSS rescore
- 2026-06-21 14:55 UTCEPSS rescore
- 2026-06-21 01:58 UTCEPSS rescore
- 2026-06-21 01:58 UTCEPSS rescore
- 2026-06-19 19:24 UTCEPSS rescore
- 2026-06-19 19:24 UTCEPSS rescore
- 2026-06-18 17:51 UTCEPSS rescore
- 2026-06-17 17:52 UTCEPSS rescore
- 2026-06-17 17:51 UTCEPSS rescore
- 2026-06-16 17:51 UTCEPSS rescore
- 2026-06-16 17:51 UTCEPSS rescore
- 2026-06-15 17:47 UTCEPSS rescore
- 2026-06-14 23:16 UTCEPSS rescore
Frequently asked(5)
What is CVE-2024-1013?
When was CVE-2024-1013 disclosed?
Is CVE-2024-1013 actively exploited?
What is the CVSS score of CVE-2024-1013?
How do I remediate CVE-2024-1013?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-1013
Is Your Infrastructure Affected by CVE-2024-1013?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.