Skip to content
Fencer Vulns
medium 5.9

CVE-2019-6475 json

A flaw in mirror zone validity checking can allow zone data to be spoofed

published 2019-10-17 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-16035

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 71%
public exploits
0
none known

Summary

Mirror zones are a BIND feature allowing recursive servers to pre-cache zone data provided by other servers. A mirror zone is similar to a zone of type secondary, except that its data is subject to DNSSEC validation before being used in answers, as if it had been looked up via traditional recursion, and when mirror zone data cannot be validated, BIND falls back to using traditional recursion instead of the mirror zone. However, an error in the validity checks for the incoming zone data can allow an on-path attacker to replace zone data that was validated with a configured trust anchor with forged data of the attacker's choosing. The mirror zone feature is most often used to serve a local copy of the root zone. If an attacker was able to insert themselves into the network path between a recursive server using a mirror zone and a root name server, this vulnerability could then be used to cause the recursive server to accept a copy of falsified root zone data. This affects BIND versions 9.14.0 up to 9.14.6, and 9.15.0 up to 9.15.4.

Patch / fix

  • bind Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 9.14.7-r0

alpine advisories ALPINE-CVE-2019-6475

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • bind Arch Linux 9.14.7-1

arch linux advisories AVG-1056

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-2019-6475 updated cvss 7.5

bind: A flaw in mirror zone validity checking can allow zone data to be spoofed

  • Red Hat Enterprise Linux 5 bind Red Hat Enterprise Linux 6 bind, bind-sdb, bind-libs, bind-utils, bind-chroot Red Hat Enterprise Linux 7 bind, bind-sdb, bind-libs, bind-utils, bind-chroot, bind-pkcs11, +6 more Red Hat Enterprise Linux 8 bind, bind-sdb, bind-libs, bind-utils, bind-chroot, bind-pkcs11, +7 more
    not affected: vulnerable code not present

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.36% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected products

  • ISC BIND 9

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Vulns 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.