# CVE-2022-3488: bind: Package updates are available for Amazon Linux 2023 that fix the following vulnerabilities: CVE-2022-3924: This issu... CVE-2022-3488 is fixed in 29 products on 1 platform, first by ALAS2023-2023-161, released April 13, 2023. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2022-3488 - Priority: High - CVSS: n/a (important) - EPSS: 0.1905 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Apr 13, 2023 ## Description Package updates are available for Amazon Linux 2023 that fix the following vulnerabilities: CVE-2022-3924: This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM `recursive-clients` limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.12-S1 through 9.16.36-S1. CVE-2022-38178: 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. CVE-2022-38177: 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. CVE-2022-3736: A flaw was found in Bind, where a resolver crash is possible. When stale cache and stale answers are enabled, the option stale-answer-client-timeout is set to a positive integer, and the resolver receives an RRSIG query. CVE-2022-3488: Processing of repeated responses to the same query, where both responses contain ECS pseudo-options, but where the first is broken in some way, can cause BIND to exit with an assertion failure. 'Broken' in this context is anything that would cause the resolver to reject the query response, such as a mismatch between query and answer name. This issue affects BIND 9 versions 9.11.4-S1 through 9.11.37-S1 and 9.16.8-S1 through 9.16.36-S1. CVE-2022-3094: Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. This, in turn, may cause `named` to exit due to a lack of free memory. We are not aware of any cases where this has been exploited. Memory is allocated prior to the checking of access permissions (ACLs) and is retained during the processing of a dynamic update from a client whose access credentials are accepted. Memory allocated to clients that are not permitted to send updates is released immediately upon rejection. The scope of this vulnerability is limited therefore to trusted clients who are permitted to make dynamic zone changes. If a dynamic update is REFUSED, memory will be released again very quickly. Therefore it is only likely to be possible to degrade or stop `named` by sending a flood of unaccepted dynamic updates comparable in magnitude to a query flood intended to achieve the same detrimental outcome. BIND 9.11 and earlier branches are also affected, but through exhaustion of internal resources rather than memory constraints. This may reduce performance but should not be a significant problem for most servers. Therefore we don't intend to address this for BIND versions prior to BIND 9.16. This issue affects BIND 9 versions 9.16.0 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.8-S1 through 9.16.36-S1. CVE-2022-3080: A flaw was found in the Bind package, where the resolver can crash when stale cache and stale answers are enabled, option stale-answer-client-timeout is set to 0 and there is a stale CNAME in the cache for an incoming query. By sending specific queries to the resolver, an attacker can cause named to crash. CVE-2022-2795: By flooding the target resolver with queries exploiting this flaw an attacker can significantly impair the resolver's performance, effectively denying legitimate clients access to the DNS resolution service. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bind amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-chroot amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-debugsource amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-devel amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dlz-filesystem amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dlz-filesystem-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dlz-ldap amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dlz-ldap-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dlz-mysql amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dlz-mysql-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dlz-sqlite3 amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dlz-sqlite3-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dnssec-doc amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dnssec-utils amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-dnssec-utils-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-libs amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-libs-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-license amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-pkcs11 amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-pkcs11-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-pkcs11-devel amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-pkcs11-libs amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-pkcs11-libs-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-pkcs11-utils amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-pkcs11-utils-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-utils amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | bind-utils-debuginfo amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | | Linux | python3-bind amzn 2023 | 32:9.16.38-1.amzn2023 | [ALAS2023-2023-161](https://patchblox.com/security/data/fix/linux/alas2023-2023-161.md) | Apr 13, 2023 | --- Data as of 2026-11-09T19:38:12Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.