Skip to content

← Public intelligence

Go package

github.com/miekg/dns

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5GoPublished

    Denial of Service in miekg-dns

    CVE-2017-15133 · GHSA-p55x-7x9v-q8m4

    Affected
    • Go github.com/miekg/dns < 1.0.4
    Fixed in
    1.0.4· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 1.0.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.9GoPublished

    miekg/dns insecurely generates random numbers

    CVE-2019-19794 · GHSA-44r7-7p62-q3fr

    Affected
    • Go github.com/miekg/dns < 1.1.25
    Fixed in
    1.1.25· Vendor fix available
    Issue
    The miekg Go DNS package before 1.1.25, as used in CoreDNS before 1.6.6 and other products, improperly generates random numbers because math/rand is used. The TXID becomes predictable, leading to response forgeries.

    Recommended action: Upgrade to 1.1.25 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. High, CVSS 7.5GoPublished

    miekg/dns parsing error leads to nil pointer dereference and DoS

    CVE-2018-17419 · GHSA-9jcx-pr2f-qvq5

    Affected
    • Go github.com/miekg/dns < 1.0.10
    Fixed in
    1.0.10· Vendor fix available
    Issue
    An issue was discovered in setTA in scanrr.go in the Miek Gieben DNS library before 1.0.10 for Go. A dns.ParseZone() parsing error causes a segmentation violation, leading to denial of service.

    Recommended action: Upgrade to 1.0.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →