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: 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 17
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 8 | bind | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-chroot | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-devel | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-export-devel | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-export-libs | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-libs | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-libs-lite | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-license | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-lite-devel | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-pkcs11 | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-pkcs11-devel | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-pkcs11-libs | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-pkcs11-utils | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-sdb | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-sdb-chroot | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | bind-utils | 32:9.11.36-3.el8_6.1 |
| AlmaLinux · 8 | python3-bind | 32:9.11.36-3.el8_6.1 |
Vulnerabilities 2
-
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.