latchset jwcrypto up to 1.5.5 JWE Token Compression allocation of resources

Summaryinfo

A vulnerability has been found in latchset jwcrypto up to 1.5.5 and classified as problematic. The affected element is an unknown function of the component JWE Token Compression Handler. The manipulation leads to allocation of resources. This vulnerability is referenced as CVE-2024-28102. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in latchset jwcrypto up to 1.5.5 and classified as problematic. This issue affects an unknown part of the component JWE Token Compression Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:

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.

The weakness was published 03/06/2024. The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-28102 since 03/04/2024. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 210497 (RHEL 8 : idm:DL1 and idm:client (RHSA-2024:3267)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.5.6 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (210497) and CERT Bund (WID-SEC-2024-1003). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Amazon Linux 2
• Red Hat Enterprise Linux
• SUSE Linux
• Oracle Linux
• IBM MQ
• IBM Spectrum Protect Plus

Productinfo

Vendor

• latchset

Name

• jwcrypto

Version

• 1.5.0
• 1.5.1
• 1.5.2
• 1.5.3
• 1.5.4
• 1.5.5

License

• open-source

Website

• Product: https://github.com/latchset/jwcrypto/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion