CVE-2024-1737VulnerabilityPublished 12 Aug 2024Updated 11 Oct 2026

SUSE · security update for bind

Affects SUSESource GCVE Database

Mentioned vulnerabilities

Not known to be exploited : upgrade to 4.15.30 soon.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 2.1% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.15.30

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade SUSE to 4.15.30.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=4.15.0 <4.15.30 Red Hat Red Hat OpenShift Enterprise Red Hat OpenShift Container Platform 4.15 amd64 Red Hat Enterprise Linux Red Hat Enterprise Linux AppStream (v. 9) Red Hat Enterprise Linux CRB (v. 9) src Red Hat Enterprise Linux AppStream (v. 8) Red Hat Enterprise Linux CRB (v. 8) Red Hat Enterprise Linux AppStream AUS (v.8.6) Red Hat Enterprise Linux AppStream E4S (v.8.6) Red Hat Enterprise Linux AppStream TUS (v.8.6) SUSE i686 bind-devel-32:9.16.23-18.el9_4.6.i686 bind-libs-32:9.16.23-18.el9_4.6.i686 noarch	Fixed in 4.15.30

AI-suggested

Red Hat has released official security updates for affected versions of Red Hat Enterprise Linux 9 and Red Hat OpenShift Container Platform 4.15 that address these vulnerabilities. Instructions for upgrading OpenShift clusters are provided by Red Hat. No additional mitigation steps are required beyond applying these official fixes.

Description

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly. Security Fix(es): * bind: bind9: BIND's database will be slow if a very large number of RRs exist at the same nam (CVE-2024-1737) * bind9: bind: SIG(0) can be used to exhaust CPU resources (CVE-2024-1975) * bind: bind9: Assertion failure when serving both stale cache data and authoritative zone content (CVE-2024-4076) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerabilities can lead to degraded DNS server performance, potential denial of service through CPU exhaustion, and server crashes due to assertion failures. This can impact DNS resolution reliability and availability on affected systems running vulnerable versions of BIND. No known exploits in the wild have been reported at this time.

Summary

The advisory covers three main vulnerabilities in BIND's DNS server (named) component: CVE-2024-1737 causes the BIND database to slow down significantly if a very large number of resource records exist at the same name; CVE-2024-1975 allows SIG(0) requests to be used to exhaust CPU resources; and CVE-2024-4076 triggers an assertion failure when serving both stale cache data and authoritative zone content simultaneously. These issues affect Red Hat Enterprise Linux 9 and Red Hat OpenShift Container Platform 4.15. Red Hat has issued updated packages and container images to fix these vulnerabilities. The advisory includes detailed instructions for upgrading and references to the official errata and release notes.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-457Use of Uninitialized Variable (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
Implementation · Attack Surface Reduction
Ensure that critical variables are initialized before first use.
Build and Compilation · Compilation or Build Hardening
Most compilers will complain about the use of uninitialized variables if warnings are turned on.
Implementation · Operation
When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2026, 23:16 UTC

WeaknessesCWE-400, CWE-457, CWE-617

Technical details

References

Community reviews

Related threats