CVE-2017-15107: A vulnerability was found in the implementation of DNSSEC in Dnsmasq up to and including 2.78.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.6% (FIRST EPSS); higher than 85.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: dnsmasq (Alpine:v3.10) 2.79-r0; dnsmasq (Alpine:v3.5) 2.76-r3; dnsmasq (Alpine:v3.6) 2.76-r6.
Low priority for now. Upgrade to dnsmasq (Alpine:v3.10) 2.79-r0; dnsmasq (Alpine:v3.5) 2.76-r3; dnsmasq (Alpine:v3.6) 2.76-r6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 23, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-358
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| thekelleys | dnsmasq | cpe:2.3:a:thekelleys:dnsmasq |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Simon Kelley dnsmasq
- up to and including 2.78affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- thekelleys dnsmasqup to 2.78 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | dnsmasq | before 2.79-r0 | 2.79-r0 |
| Alpine:v3.5 | dnsmasq | before 2.76-r3 | 2.76-r3 |
| Alpine:v3.6 | dnsmasq | before 2.76-r6 | 2.76-r6 |
| Alpine:v3.7 | dnsmasq | before 2.78-r2 | 2.78-r2 |
| Debian:12 | dnsmasq | before 2.79-1 | 2.79-1 |
| openSUSE:Leap 15.1 | dnsmasq | before 2.78-lp151.5.3.1 | 2.78-lp151.5.3.1 |
| openSUSE:Tumbleweed | dnsmasq | before 2.86-1.1 | 2.86-1.1 |
| SUSE:HPE Helion OpenStack 8 | dnsmasq | before 2.78-18.6.1 | 2.78-18.6.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | dnsmasq | before 2.78-3.8.1 | 2.78-3.8.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP1 | dnsmasq | before 2.78-7.3.1 | 2.78-7.3.1 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | dnsmasq | before 2.78-0.17.10.1 | 2.78-0.17.10.1 |
Same product
thekelleys: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-14491Heap-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execute arbitrary code…65This week
- CVE-2020-25681A flaw was found in dnsmasq before version 2.83.58Plan
- CVE-2020-25682A flaw was found in dnsmasq before 2.83.55Plan
Published before and after this one in the same product
- ← EarlierCVE-2013-0198Mar 5, 2013 · Dnsmasq before 2.66test2, when used with certain libvirt configurations, replies to queries from prohibited interfaces, which allows remote…21Monitor
- ← EarlierCVE-2015-3294May 8, 2015 · The tcp_request function in Dnsmasq before 2.73rc4 does not properly handle the return value of the setup_reply function, which allows…26Monitor
- Later →CVE-2019-14513Aug 1, 2019 · Improper bounds checking in Dnsmasq before 2.76 allows an attacker controlled DNS server to send large DNS packets that result in a read…31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:dnsmasq | 2.79-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:dnsmasq | 2.79-1 · Debian:12 | Package registry (OSV) |
| opensuse:dnsmasq | 2.78-lp151.5.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| suse:dnsmasq | 2.78-0.17.10.1 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-358 · Improperly Implemented Security Check for StandardCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.