{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-6475 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-6475 is a medium-severity vulnerability in Isc Bind, published on 17 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-6475 and fix it if it is affected.\n\nWhat it is: CVE-2019-6475 is a medium-severity vulnerability in Isc Bind, published on 17 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-6475 in the wild and no public exploit code.\n\nAffected product: Isc Bind. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-6475/ (Markdown: https://insights.sbomify.com/CVE-2019-6475/index.md)","id":"CVE-2019-6475","markdown":"https://insights.sbomify.com/CVE-2019-6475/index.md","name":"CVE-2019-6475","record":{"aliases":["ALPINE-CVE-2019-6475","GHSA-2gfp-93f7-f268"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"BIND DNS server","requires_auth":"none","summary":"An on-path attacker can spoof DNS data in BIND mirror zones by bypassing validity checks, requiring the mirror zone feature to be enabled.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"isc","cpe":[{"product":"bind","vendor":"isc"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"A flaw in mirror zone validity checking can allow zone data to be spoofed","id":"CVE-2019-6475","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"isc:bind","products":["isc:bind"],"type":"other","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"An error in QNAME minimization code can cause BIND to exit with an assertion failure","id":"CVE-2019-6476"},"packages":[],"prev":{"headline":"A packet containing a malformed DUID can cause the kea-dhcp6 server to terminate","id":"CVE-2019-6474"},"products":["BIND 9"],"published":"2019-10-17","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-0122","kev_date_added":null,"published":"2008-01-16"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0010","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0011","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0013","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2000-1029","kev_date_added":null,"published":"2000-11-29"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-1999-0837","kev_date_added":null,"published":"2000-01-04"},{"cvss_score":8.5,"headline":"Denial of service in n/a","id":"CVE-2012-1667","kev_date_added":null,"published":"2012-06-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["ISC"]},"summary":"An on-path attacker can spoof DNS data in BIND mirror zones by bypassing validity checks, requiring the mirror zone feature to be enabled.","url":"https://insights.sbomify.com/CVE-2019-6475/"}