Remote service crash via premature TLS socket destruction
Published May 19, 2022 · Updated Sep 17, 2024
Denial of service in BIND 9 9.18.0 through 9.18.2 and 9.19.0 allows remote attackers to crash named via an early TLS disconnect. A configured HTTP TLS listener with a defined endpoint destroys a TLS socket object prematurely, triggering an assertion failure in named. The daemon is exposed only when named.conf references http in a listen-on statement; DNS over TLS without DNS over HTTPS is unaffected.
Summary
What happened
Denial of service in BIND 9 9.18.0 through 9.18.2 and 9.19.0 allows remote attackers to crash named via an early TLS disconnect. A configured HTTP TLS listener with a defined endpoint destroys a TLS socket object prematurely, triggering an assertion failure in named. The daemon is exposed only when named.conf references http in a listen-on statement; DNS over TLS without DNS over HTTPS is unaffected.
The record
- CVE
- CVE-2022-1183
- Published
- May 19, 2022
- Updated
- Sep 17, 2024
- Vendor
- Internet Systems Consortium
- Product
- BIND 9
- Classifications
- CWE-617, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Development Branch 9.19 9.19.0
- Affected versionversion=Open Source Branch 9.18 9.18.0 through versions before 9.18.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo