CVE-2021-25218
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
- State
- Published
- Severity
- 7.5 High
- Published
- Aug 18, 2021
- Updated
- Sep 17, 2024
- Reserved
- Jan 15, 2021
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 7.5 High | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | isc |
Weaknesses
The record names no weakness.
Affected Products
| Product | Versions |
|---|---|
BIND9ISC |
|
References
- https://kb.isc.org/v1/docs/cve-2021-25218
- [oss-security] 20210818 ISC has disclosed a vulnerability in BIND (CVE-2021-25218)mailing-list
- [oss-security] 20210820 August BIND maintenance releases contain a defect affecting servers using the map zone file format (was: A vulnerability in BIND (CVE-2021-25218) will be announced 18 August 2021)mailing-list
- FEDORA-2021-fbb258debfvendor-advisory
- https://security.netapp.com/advisory/ntap-20210909-0002/
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.