# CVE-2017-15107: Security feature bypass in dnsmasq

> Attackers can bypass DNSSEC validation to spoof hostnames, affecting Dnsmasq users relying on secure DNS resolution.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-15107, CLEANSTART-2026-ND09534, DEBIAN-CVE-2017-15107, GHSA-f999-2m22-345j, SUSE-SU-2019:14190-1, SUSE-SU-2019:1721-1, UBUNTU-CVE-2017-15107

## What is CVE-2017-15107?

CVE-2017-15107 is a high-severity vulnerability in Simon Kelley dnsmasq, published on 23 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in the implementation of DNSSEC in Dnsmasq up to and including 2.78. Wildcard synthesized NSEC records could be improperly interpreted to prove the non-existence of hostnames that actually exist.

Weakness: CWE-358 (Improperly Implemented Security Check for Standard)

## Which versions are affected by CVE-2017-15107?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dnsmasq` | SUSE:HPE Helion OpenStack 8 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:Linux Enterprise Server 11 SP4-LTSS | All versions | 2.78-0.17.10.1 |
| `dnsmasq` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:OpenStack Cloud 7 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:OpenStack Cloud 8 | All versions | 2.78-18.6.1 |
| `dnsmasq` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 2.78-18.6.1 |

Products: Thekelleys Dnsmasq.

## How do I fix CVE-2017-15107?

Upgrade to a fixed version.

## Is CVE-2017-15107 being exploited?

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

## Other vulnerabilities in Simon Kelley dnsmasq

- [CVE-2021-45951](https://insights.sbomify.com/CVE-2021-45951/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-45952](https://insights.sbomify.com/CVE-2021-45952/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-45953](https://insights.sbomify.com/CVE-2021-45953/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-45954](https://insights.sbomify.com/CVE-2021-45954/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-45955](https://insights.sbomify.com/CVE-2021-45955/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15107 and fix it if it is affected.

What it is: CVE-2017-15107 is a high-severity vulnerability in Simon Kelley dnsmasq, published on 23 Jan 2018. 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-2017-15107 in the wild and no public exploit code.

Affected product: Simon Kelley dnsmasq. 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-2017-15107/ (Markdown: https://insights.sbomify.com/CVE-2017-15107/index.md)
```

## Sources

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

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