CVE-2024-38229VulnerabilityPublished 9 Oct 2024Updated 11 Oct 2026

SUSE · security update for dotnet8.0

Affects SUSESource GCVE Database

Mentioned vulnerabilities

Not known to be exploited · patch available : update SUSE when convenient.

Data as of 26 Oct 2026, 08:30 UTC

Severity

Low

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

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

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Oct 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 26 Oct 2026.

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

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected Red Hat Red Hat Enterprise Linux Red Hat Enterprise Linux AppStream (v. 9) Red Hat Enterprise Linux CRB (v. 9) aarch64 SUSE x86_64 aspnetcore-runtime-8.0-0:8.0.10-1.el9_4.x86_64 aspnetcore-runtime-dbg-8.0-0:8.0.10-1.el9_4.x86_64 aspnetcore-targeting-pack-8.0-0:8.0.10-1.el9_4.x86_64	Fixed in–

AI-suggested

An official fix is available from Red Hat. Users should update to .NET SDK 8.0.110 and .NET Runtime 8.0.10 as provided in Red Hat Enterprise Linux 9 updates. Refer to the Red Hat advisory RHSA-2024:7869 and the article https://access.redhat.com/articles/11258 for detailed update instructions. Applying these updates will remediate the vulnerabilities. No additional mitigation is required beyond applying the official patches.

Description

.NET is a managed-software framework. It implements a subset of the .NET framework APIs and several new APIs, and it includes a CLR implementation. New versions of .NET that address a security vulnerability are now available. The updated versions are .NET SDK 8.0.110 and .NET Runtime 8.0.10. Security Fix(es): * dotnet: kestrel: closing an HTTP/3 stream can cause a race condition and lead to remote code execution (CVE-2024-38229) * dotnet: Multiple .NET components susceptible to hash flooding (CVE-2024-43483) * dotnet: System.IO.Packaging - Multiple DoS vectors in use of SortedList (CVE-2024-43484) * dotnet: Denial of Service in System.Text.Json (CVE-2024-43485) 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.Security Fix(es): * dotnet: System.IO.Packaging - Multiple DoS vectors in use of SortedList (CVE-2024-43484) * dotnet: Multiple .NET components susceptible to hash flooding (CVE-2024-43483) * dotnet: Denial of Service in System.Text.Json (CVE-2024-43485) * dotnet: kestrel: closing an HTTP/3 stream can cause a race condition and lead to remote code execution (CVE-2024-38229) 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

Successful exploitation of CVE-2024-38229 can lead to remote code execution due to a race condition in Kestrel HTTP/3 stream handling. The other vulnerabilities (CVE-2024-43483, CVE-2024-43484, CVE-2024-43485) can cause denial of service conditions through hash flooding and resource exhaustion in .NET components. These impacts can disrupt service availability and compromise system integrity. The CVSS vector for CVE-2024-38229 indicates high confidentiality, integrity, and availability impact with network attack vector and no privileges required.

Summary

.NET 8.0 on Red Hat Enterprise Linux 9 contains multiple security vulnerabilities. CVE-2024-38229 describes a race condition in the Kestrel HTTP/3 stream closure that can lead to remote code execution. CVE-2024-43483 involves hash flooding vulnerabilities affecting multiple .NET components. CVE-2024-43484 and CVE-2024-43485 describe denial of service issues in System.IO.Packaging (due to SortedList usage) and System.Text.Json respectively. Red Hat has issued official patches in .NET SDK 8.0.110 and .NET Runtime 8.0.10 to address these vulnerabilities. The advisory rates the overall impact as Important with a high severity CVSS vector for CVE-2024-38229. No known exploits in the wild have been reported. The affected platforms include Red Hat Enterprise Linux 9 variants across multiple architectures (x86_64, s390x, ppc64le, aarch64).

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-407Inefficient Algorithmic Complexity (opens in a new tab)
Class weaknessLikelihood of exploit: Low
An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
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.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
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 4 Jul 2026, 01:18 UTC

WeaknessesCWE-416, CWE-407, CWE-770

Technical details

References

Community reviews

Related threats