CVE-2024-28102 | JWCrypto vulnerable to JWT bomb Attack in `deserialize` function

Exp

JWCrypto implements JWK, JWS, and JWE specifications using python-cryptography. Prior to version 1.5.6, an attacker can cause a denial of service attack by passing in a malicious JWE Token with a high compression ratio. When the server processes this token, it will consume a lot of memory and processing time. Version 1.5.6 fixes this vulnerability by limiting the maximum token length.

Published: 2024-03-21 Last update: 2025-12-22 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-28102 is rated High Exploit Risk (63.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.38%). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-28102

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-28102

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-25 0.28% 0.38% +0.10%
2 2026-01-18 0.19% 0.28% +0.09%
3 2025-12-23 — 0.19% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-28102

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.3 4.0 [email protected]

Weakness enumeration for CVE-2024-28102

GitHub Security Advisory for CVE-2024-28102

GHSA-j857-7rvv-vj97 · Severity: medium · Ecosystem: pip — JWCrypto vulnerable to JWT bomb Attack in `deserialize` function

OS Trackers for CVE-2024-28102

vendor priority summary link
debian not yet assigned CVE-2024-28102 not yet assigned priority: Debian including 1 source packages (python-jwcrypto), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-28102
redhat medium — https://access.redhat.com/security/cve/CVE-2024-28102
suse medium — https://www.suse.com/security/cve/CVE-2024-28102/
ubuntu medium CVE-2024-28102 medium priority: Ubuntu including 1 source packages (python-jwcrypto), 10 status rows across 10 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, upstream, xenial): needs-triage 7, ignored 3. https://ubuntu.com/security/CVE-2024-28102

Affected software / configurations for CVE-2024-28102

Vendor Product Version Raw CPE
latchset jwcrypto < 1.5.6 cpe:2.3:a:latchset:jwcrypto:*:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2024-28102

cvelogic Threat Intelligence