dbcve.org
Miekg DnsApplication · Miekg Dns Prject

CVE-2017-15133

HIGH · 7.5 CVSS v3.0 Published 2018-01-29
Fix available
A fix is available. Upgrade to 1.0.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial of service vulnerability exists in miekg-dns versions before 1.0.4. Remote attackers can send carefully timed TCP packets to exhaust server resources and prevent the DNS server from accepting new legitimate connections.

MitigationUpgrade miekg-dns to version 1.0.4 or later to patch the vulnerability. As a compensating control, implement connection rate limiting and monitoring to detect and block abnormal connection patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Miekg DnsApplication
Affected:< 1.0.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify miekg-dns usage
    Search your codebase, dependencies, or installed packages for 'miekg-dns' or 'github.com/miekg/dns' to confirm the library is in use
    Affected if miekg-dns is present in your environment
  2. Find installed version
    Run a dependency query such as 'go list -m all' for Go projects, or inspect your lockfile (go.mod, vendor/, Gopkg.lock) for the miekg-dns version
    Affected if version is below 1.0.4 (e.g., 1.0.3, 1.0.2, etc.)
  3. Verify TCP handling is enabled
    Check your DNS server configuration or code for TCP listener setup (look for 'tcp' in Listen, Serve, or server startup parameters)
    Affected if TCP handling is enabled and the server accepts TCP connections on port 53
  4. Check network exposure
    Review firewall rules or network accessibility to confirm the DNS service is reachable from untrusted networks
    Affected if TCP port 53 is exposed to the internet or untrusted networks

Your environment is affected if miekg-dns version is below 1.0.4 AND your DNS server accepts TCP connections that are reachable by remote attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.0.4 or later
Fixed in 1.0.4
Interim mitigation

Upgrade miekg-dns to version 1.0.4 or later to patch the vulnerability. As a compensating control, implement connection rate limiting and monitoring to detect and block abnormal connection patterns.

Fix this in Miekg Dns Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-15133 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data