CyberRota Analysis
AI-GeneratedBIND is vulnerable to a flaw where it accepts an invalid data structure in DNS records, specifically when a PRIVATEDNS algorithm is improperly defined with an incorrect length for the identifier. This can lead to BIND aborting and exiting during processing, potentially disrupting DNS services. Organizations using affected versions of BIND should prioritize patching to mitigate the risk of service interruptions.
Original NVD Description
If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit. BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the algorithm identifier, improperly give a length longer than the actual identifier data. The invalid identifier will be stored. If BIND later needs to render that record to text, it will use the invalid length during processing, leading to a consistency check failing. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.