Alpine: multiple bind packages: security update to 9.18.11-r0

high Tenable Cloud Security Plugin ID 423712

Description

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

- 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-3094)

- BIND 9 resolver can crash when stale cache and stale answers are enabled, option `stale-answer-client-
timeout` is set to a positive integer, and the resolver receives an RRSIG query. 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-3736)

- 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-3924)

Plugin Details

Severity: High

ID: 423712

Version: Revision 1.10

Type: Local

Family: Alpine Linux Local Security Checks

Published: 4/4/2025

Updated: 7/2/2026

Supported Sensors: Agentless Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.51

CVSS v2

Risk Factor: High

Base Score: 7.8

Temporal Score: 5.8

Vector: CVSS2#AV:N/AC:L/Au:N/C:N/I:N/A:C

CVSS Score Source: CVE-2022-3924

CVSS v3

Risk Factor: High

Base Score: 7.5

Temporal Score: 6.5

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

Exploit Ease: No known exploits are available

Vulnerability Publication Date: 1/25/2023

Reference Information

CVE: CVE-2022-3094, CVE-2022-3736, CVE-2022-3924

IAVA: 2023-A-0058-S

Detections

Analytics