CVE-2022-0635

Description

Versions affected: BIND 9.18.0 When a vulnerable version of named receives a series of specific queries, the named process will eventually terminate due to a failed assertion check.

Remediation

Solution:

  • Users of BIND 9.18.0 should upgrade to BIND 9.18.1

Workaround:

  • The failure can be avoided by adding this option to named.conf: synth-from-dnssec no;

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.91% Top 30%
Vendor Advisory isc.org
Affected: ISC BIND
Published at:
Updated at:

References

Link Tags
https://kb.isc.org/v1/docs/cve-2022-0635 mitigation vendor advisory
https://security.netapp.com/advisory/ntap-20220408-0001/ third party advisory

Frequently Asked Questions

What is the severity of CVE-2022-0635?
CVE-2022-0635 has been scored as a high severity vulnerability.
How to fix CVE-2022-0635?
To fix CVE-2022-0635: Users of BIND 9.18.0 should upgrade to BIND 9.18.1
Is CVE-2022-0635 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-0635 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-0635?
CVE-2022-0635 affects ISC BIND.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.