Skip to content
OpenAdvisories
High · 7.5 CVE-2021-25218 EUVD-2021-12129GHSA-cc8x-chx9-c63q

A too-strict assertion check could be triggered when responses in BIND 9.16.19 and 9.17.16 require UDP fragmentation if RRL is in use

Published Aug 18, 2021 · Updated Sep 17, 2024 · Assigned by isc

Description

In BIND 9.16.19, 9.17.16. Also, version 9.16.19-S1 of BIND Supported Preview Edition When a vulnerable version of named receives a query under the circumstances described above, the named process will terminate due to a failed assertion check. The vulnerability affects only BIND 9 releases 9.16.19, 9.17.16, and release 9.16.19-S1 of the BIND Supported Preview Edition.

Affected products

VendorProductAffectedFixed
ISC BIND9 Stable Branch 9.16.19, Development Branch 9.17.16, Supported Preview Edition 9.16.19-S1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
openSUSE Tumbleweed bind 9.16.20-1.4 openSUSE-SU-2024:10650-1
ReleasePackageFixed inAdvisory
Alpine v3.24 bind 9.16.20-r0 —
Alpine v3.23 bind 9.16.20-r0 —
Alpine v3.22 bind 9.16.20-r0 —
Alpine v3.21 bind 9.16.20-r0 —
Alpine v3.20 bind 9.16.20-r0 —
Show 9 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Alpine v3.19 bind 9.16.20-r0 —
Alpine v3.18 bind 9.16.20-r0 —
Alpine v3.17 bind 9.16.20-r0 —
Alpine v3.16 bind 9.16.20-r0 —
Alpine v3.15 bind 9.16.20-r0 —
Alpine v3.14 bind 9.16.20-r0 —
Alpine v3.13 bind 9.16.20-r0 —
Alpine v3.12 bind 9.16.20-r0 —
Alpine v3.11 bind 9.16.20-r0 —

Advisories 1

References