CVE-2024-1737: BIND's database will be slow if a very large number of RRs exist at the same name

Published Jul 19, 2024
·
Updated

BIND's database will be slow if a very large number of RRs exist at the same name

Other sources

ISC BIND is vulnerable to a denial of service, caused by an error when content is being added or updated in resolver caches and authoritative zone databases that hold significant numbers of RRs for the same hostname (of any RTYPE). By processing queries, a remote attacker could exploit this vulnerability to cause the database to slow down.

IBM

Resolver caches and authoritative zone databases that hold significant numbers of RRs for the same hostname (of any RTYPE) can suffer from degraded performance as content is being added or updated, and also when handling client queries for this name. This issue affects BIND 9 versions 9.11.0 through 9.11.37, 9.16.0 through 9.16.50, 9.18.0 through 9.18.27, 9.19.0 through 9.19.24, 9.11.4-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.50-S1, and 9.18.11-S1 through 9.18.27-S1.

NVD

Resolver caches and authoritative zone databases that hold significant numbers of RRs for the same hostname (of any RTYPE) can suffer from degraded performance as content is being added or updated, and also when handling client queries for this name. This vulnerability affects the following bind versions: 9.11.0 -> 9.11.37 9.16.0 -> 9.16.50 9.18.0 -> 9.18.27 9.19.0 -> 9.19.24

Red Hat

Affected Software

5 affected componentsFixes available
debian/bind9
1:9.16.50-1~deb11u21:9.16.50-1~deb11u31:9.18.33-1~deb12u21:9.20.8-6
Microsoft cbl2 dhcp 4.4.3.P1-2
Microsoft cbl2 bind 9.16.50-1
Microsoft azl3 bind 9.19.21-1
Microsoft azl3 bind 9.20.0-1

Remediation

Information

Upgrade to the patched release most closely related to your current version of BIND 9: 9.18.28, 9.20.0, or 9.18.28-S1.

Event History

Jul 15, 2024
News Published
02:01 AM
Jul 19, 2024
Data Sourced
via Red Hat·05:17 PM
DescriptionSeverityAffected Software
Jul 23, 2024
CVE Published
via MITRE·02:34 PM
Data Sourced
via MITRE·02:34 PM
RemedyDescriptionSeverity
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeakness
Jul 29, 2024
News Published
01:58 AM
Aug 15, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Sep 13, 2024
Data Sourced
via Ubuntu·04:38 PM
RemedyDescriptionSeverityAffected Software
Feb 4, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Jul 6, 2025
News Published
via The Register·08:10 PM
News Published
via The Register·08:14 PM

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-1737?

CVE-2024-1737 is rated as a moderate severity vulnerability due to performance degradation issues.

2

How do I fix CVE-2024-1737?

To fix CVE-2024-1737, update to the latest version of the BIND9 package that addresses the performance issues.

3

Which versions of BIND9 are affected by CVE-2024-1737?

CVE-2024-1737 affects BIND9 versions 1:9.16.50-1~deb11u2, 1:9.16.50-1~deb11u1, 1:9.18.28-1~deb12u2, 1:9.20.4-3, and 1:9.20.4-4.

4

What type of systems are impacted by CVE-2024-1737?

CVE-2024-1737 impacts systems running the BIND9 DNS server software.

5

Can CVE-2024-1737 lead to denial of service conditions?

While CVE-2024-1737 primarily affects performance, degraded responsiveness may lead to service availability issues.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203