# CVE-2024-24192: Memory corruption in n/a

> A heap overflow in the robdns library allows attackers to execute arbitrary code or cause denial of service via crafted zone files.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-26ch-39wc-5m9p

## What is CVE-2024-24192?

CVE-2024-24192 is a low-severity memory corruption vulnerability in n/a, published on 6 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

robdns commit d76d2e6 was discovered to contain a heap overflow via the component block->filename at /src/zonefile-insertion.c.

Weakness: CWE-125 (Out-of-bounds Read), CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Robertdavidgraham Robdns.

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

No fix has been published for CVE-2024-24192 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-24192 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-24195](https://insights.sbomify.com/CVE-2024-24195/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24192 is a low-severity memory corruption vulnerability in n/a, published on 6 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-24192 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-24192/ (Markdown: https://insights.sbomify.com/CVE-2024-24192/index.md)
```

## Sources

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

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