CVE-2024-1013

CVE-2024-1013 is a high-severity vulnerability in Unixodbc with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-823.

Key facts

Description

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.

Frequently asked questions

What is CVE-2024-1013?
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.
How severe is CVE-2024-1013?
CVE-2024-1013 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-1013 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-1013?
CVE-2024-1013 affects Unixodbc. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-1013?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-1013 have an EU (EUVD) identifier?
Yes. CVE-2024-1013 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-16790.
When was CVE-2024-1013 published?
CVE-2024-1013 was published on 2024-03-18 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Unixodbc

All CVEs affecting Unixodbc →

Other CWE-823 vulnerabilities

Browse all CWE-823 vulnerabilities →