Summary
The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.
Security Fix(es):
* bind: BIND 9 resolvers configured to answer from cache with zero stale-answer-timeout may terminate unexpectedly (CVE-2022-3080)
* bind: memory leak in ECDSA DNSSEC verification code (CVE-2022-38177)
* bind: memory leaks in EdDSA DNSSEC verification code (CVE-2022-38178)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Fixed packages 9
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 9 | bind | 32:9.16.23-1.el9_0.1 |
| AlmaLinux · 9 | bind-chroot | 32:9.16.23-1.el9_0.1 |
| AlmaLinux · 9 | bind-devel | 32:9.16.23-1.el9_0.1 |
| AlmaLinux · 9 | bind-dnssec-doc | 32:9.16.23-1.el9_0.1 |
| AlmaLinux · 9 | bind-dnssec-utils | 32:9.16.23-1.el9_0.1 |
| AlmaLinux · 9 | bind-libs | 32:9.16.23-1.el9_0.1 |
| AlmaLinux · 9 | bind-license | 32:9.16.23-1.el9_0.1 |
| AlmaLinux · 9 | bind-utils | 32:9.16.23-1.el9_0.1 |
| AlmaLinux · 9 | python3-bind | 32:9.16.23-1.el9_0.1 |
Vulnerabilities 3
-
High 7.5
BIND 9 resolvers configured to answer from stale cache with zero stale-answer-client-timeout may terminate unexpectedly
By sending specific queries to the resolver, an attacker can cause named to crash.
-
High 7.5
Memory leak in ECDSA DNSSEC verification code
By spoofing the target resolver with responses that have a malformed ECDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources.
-
High 7.5
Memory leaks in EdDSA DNSSEC verification code
By spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources.
References
-
report
https://access.redhat.com/security/cve/CVE-2022-3080
-
report
https://access.redhat.com/security/cve/CVE-2022-38177
-
report
https://access.redhat.com/security/cve/CVE-2022-38178
-
report
https://bugzilla.redhat.com/2128600
-
report
https://bugzilla.redhat.com/2128601
-
report
https://bugzilla.redhat.com/2128602
-
advisory
https://errata.almalinux.org/9/ALSA-2022-6763.html