# CVE-2019-14513: Memory corruption in n/a

> An attacker-controlled DNS server can trigger a buffer over-read in Dnsmasq, potentially causing denial of service or code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-14513, DLA-1921-1, GHSA-8x2j-2xxw-g7h5, RHBA-2017:2117, UBUNTU-CVE-2019-14513

## What is CVE-2019-14513?

CVE-2019-14513 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 1 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper bounds checking in Dnsmasq before 2.76 allows an attacker controlled DNS server to send large DNS packets that result in a read operation beyond the buffer allocated for the packet, a different vulnerability than CVE-2017-14491.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-14513?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dnsmasq` | Red Hat:enterprise_linux:7::client | All versions | 0:2.76-2.el7 |
| `dnsmasq-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.76-2.el7 |
| `dnsmasq-utils` | Red Hat:enterprise_linux:7::client | All versions | 0:2.76-2.el7 |
| `dnsmasq` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.76-2.el7 |
| `dnsmasq-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.76-2.el7 |
| `dnsmasq-utils` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.76-2.el7 |
| `dnsmasq` | Red Hat:enterprise_linux:7::server | All versions | 0:2.76-2.el7 |
| `dnsmasq-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:2.76-2.el7 |
| `dnsmasq-utils` | Red Hat:enterprise_linux:7::server | All versions | 0:2.76-2.el7 |
| `dnsmasq` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.76-2.el7 |
| `dnsmasq-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.76-2.el7 |
| `dnsmasq-utils` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.76-2.el7 |

Products: Debian Debian Linux, Thekelleys Dnsmasq.

## How do I fix CVE-2019-14513?

Upgrade to a fixed version.

## Is CVE-2019-14513 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14513 and fix it if it is affected.

What it is: CVE-2019-14513 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 1 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-14513 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2019-14513/ (Markdown: https://insights.sbomify.com/CVE-2019-14513/index.md)
```

## Sources

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

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