# CVE-2024-1013: Unixodbc: out of bounds stack write due to pointer-to-integer types conversion

> An out-of-bounds stack write in unixODBC on 64-bit systems allows attackers to potentially execute code or cause denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2024
- **Updated:** 20 Nov 2025
- **Also known as:** AZL-36896, AZL-36904, BIT-unixodbc-2024-1013, CLSA-2024-1712261674, CLSA-2024-1712262573, CLSA-2024-1712263690, CLSA-2024-1712490771, CLSA-2024-1712837462, CLSA-2024-1714462946, CLSA-2025-1761844758, DEBIAN-CVE-2024-1013, ECHO-b798-34bb-79d9, GHSA-x6h9-cx79-jjjv, MGASA-2024-0106, MINI-83mw-7h56-m733, OESA-2024-1327, OESA-2024-1370, OESA-2024-1371, OESA-2024-1372, OESA-2024-1373, OESA-2024-1374, OESA-2024-2332, ROOT-OS-DEBIAN-12-CVE-2024-1013, SUSE-SU-2024:2978-1, UBUNTU-CVE-2024-1013, USN-6715-1, USN-6715-2

## What is CVE-2024-1013?

CVE-2024-1013 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 6, published on 18 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-823 (Use of Out-of-range Pointer Offset)

## Which versions are affected by CVE-2024-1013?

1 open source package ship an affected version, including unixodbc. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `unixodbc` | Bitnami | All versions | None |
| `unixODBC` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 2.3.9-7.16.1 |
| `unixODBC` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 2.3.9-7.16.1 |
| `unixODBC` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 2.3.9-7.16.1 |

Products: Unixodbc Unixodbc.

## How do I fix CVE-2024-1013?

Apply the vendor's patch.

## Is CVE-2024-1013 being exploited?

There is no known exploitation of CVE-2024-1013 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat Enterprise Linux 6

- [CVE-2018-7485](https://insights.sbomify.com/CVE-2018-7485/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-7409](https://insights.sbomify.com/CVE-2018-7409/): Memory corruption in n/a (critical 9.8)
- [CVE-2012-2657](https://insights.sbomify.com/CVE-2012-2657/): Memory corruption in n/a (low 2.1)
- [CVE-2012-2658](https://insights.sbomify.com/CVE-2012-2658/): Memory corruption in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1013 and fix it if it is affected.

What it is: CVE-2024-1013 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 6, published on 18 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1013 in the wild and no public exploit code.

Affected packages and fixed versions:
- unixodbc (Bitnami): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1013/ (Markdown: https://insights.sbomify.com/CVE-2024-1013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1013
- OSV: https://osv.dev/vulnerability/CVE-2024-1013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1013/
Summaries are generated and may contain mistakes; the official description above is the record.
