Skip to content
Fencer Intel
high 7.5

CVE-2017-15133 json

Denial of Service in miekg-dns

published 2018-01-29 8 y ago modified 2026-06-17 4 mo ago also GHSA-p55x-7x9v-q8m4 , GO-2020-0006 , EUVD-2021-1368

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

A denial of service flaw was found in miekg-dns before 1.0.4. A remote attacker could use carefully timed TCP packets to block the DNS server from accepting new connections.

Patch / fix

  • go github.com/miekg/dns 1.0.4, 1.0.4-0.20180125103619-43913f2f4fbd
  • miekg-dns_prject miekg-dns 1.0.4
  • golang-github-miekg-dns Debian 14, Debian 13, Debian 12 0.0~git20170501.0.f282f80-3

debian advisories DEBIAN-CVE-2017-15133

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-15133 updated cvss 7.5

miekg-dns: Denial of service via TCP serving code

  • Red Hat OpenShift Enterprise 3 miekg-dns
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.85% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/miekg/dns
<1.0.4
<1.0.4-0.20180125103619-43913f2f4fbd
1.0.4
1.0.4-0.20180125103619-43913f2f4fbd

Affected products

  • Miek Gieben miekg-dns

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.