JWCrypto vulnerable to JWT bomb Attack in `deserialize` function
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.8epss 1.0%
exploitation probability
1.0%top 39% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H
Affected products
latchset · jwcryptoReferences
https://github.com/latchset/jwcrypto/commit/90477a3b6e73da69740e00b8161f53fea19b831fhttps://github.com/latchset/jwcrypto/security/advisories/GHSA-j857-7rvv-vj97https://lists.debian.org/debian-lts-announce/2024/09/msg00026.htmlhttps://www.vicarius.io/vsociety/posts/denial-of-service-vulnerability-discovered-in-jwcrypto-cve-2024-28102-28103