LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19794: The miekg Go DNS package before 1.1.25, as used in CoreDNS before 1.6.6 and other products, improperly gene...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects DNS software that used weak random number generation for DNS transaction IDs. Predictable IDs can let an attacker forge DNS responses in some conditions, potentially redirecting users or services. Public sources identify miekg/dns before 1.1.25 and CoreDNS before 1.6.6; broader downstream impact is not fully enumerated.

Executive priority

Treat this as a targeted DNS integrity risk, not a confirmed emergency. Prioritize remediation for DNS infrastructure, Kubernetes/CoreDNS environments, and services where forged DNS responses could affect authentication, routing, or customer traffic.

Technical view

CVE-2019-19794 is a predictable DNS TXID issue caused by use of Go math/rand in miekg/dns before 1.1.25. CoreDNS before 1.6.6 used the affected package. Predictable transaction IDs reduce entropy needed for DNS response forgery. Source data does not provide CVSS, CWE, or detailed exploitation prerequisites.

Likely exposure

Exposure is most likely in Go applications, DNS tooling, or DNS infrastructure that directly or transitively uses github.com/miekg/dns below v1.1.25, including CoreDNS deployments below 1.6.6. Other products may be affected, but the provided sources do not identify them.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The risk is practical where an attacker can race or inject forged DNS responses and the resolver path depends on affected TXID generation. Evidence is insufficient to claim broad exploitation.

Researcher notes

The core issue is weak TXID randomness, not a memory corruption bug. Public metadata lacks CVSS and detailed exploit conditions. Validate exposure through dependency and runtime version checks, then map whether the affected code is used for DNS queries in reachable paths.

Mitigation direction

  • Upgrade miekg/dns dependencies to v1.1.25 or later.
  • Upgrade CoreDNS deployments to v1.6.6 or later where applicable.
  • Check vendor guidance for products bundling miekg/dns.
  • Prioritize internet-facing or security-critical DNS components first.
  • Track transitive dependency updates through SBOM or dependency tooling.

Validation and detection

  • Identify direct dependencies on github.com/miekg/dns below v1.1.25.
  • Check CoreDNS binaries, images, or manifests for versions below 1.6.6.
  • Review SBOMs for transitive miekg/dns usage.
  • Confirm rebuilt artifacts resolve to fixed dependency versions.
  • Document any third-party product exposure pending vendor confirmation.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-19794 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.