CVE-2024-28102VulnerabilityPublished 30 Apr 2024Updated 11 Oct 2026

SUSE · security update for python-jwcrypto

Affects SUSESource GCVE Database

Not known to be exploited · fixed in 9.8 : update SUSE when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

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

EPSS: 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.8, 9.6, 9.4

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Apr 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-25.

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 9.8, 9.6 or 9.4.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=9.0 <9.4 >=9.4 <9.6 >=9.6 <9.8	Fixed in 9.4 9.6 9.8

AI-suggested

A security update fixing this vulnerability is available from Red Hat. Users should apply the updated python-jwcrypto packages as provided in Red Hat Advisory RHSA-2024:2559. Ensure all previously released errata relevant to the system are applied before updating. No additional mitigation steps are indicated by the vendor.

Description

A denial of service vulnerability (CVE-2024-28102) exists in the python-jwcrypto package used in Red Hat Enterprise Linux 9 and related distributions. The issue occurs when processing malicious JSON Web Encryption (JWE) tokens, causing the application to become unresponsive. Red Hat has issued security updates to address this vulnerability. The fix is available and should be applied to affected systems to prevent denial of service conditions.

Impact

Successful exploitation of this vulnerability can cause affected applications using python-jwcrypto to become unresponsive, resulting in a denial of service condition. There is no indication of code execution or data compromise from the provided information.

Summary

CVE-2024-28102 is a denial of service vulnerability in the python-jwcrypto package, which implements JSON Web Key (JWK), JSON Web Signature (JWS), JSON Web Encryption (JWE), and JSON Web Token (JWT) standards. The vulnerability arises from processing specially crafted malicious JWE tokens that can cause the application to hang or become unresponsive. Red Hat has released updated python-jwcrypto packages for Red Hat Enterprise Linux 9 and related variants to remediate this issue.

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).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:37 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats