joaquimserafim json-web-token prior 3.1.1 JSON Web Token data authenticity

Summaryinfo

A vulnerability classified as problematic was found in joaquimserafim json-web-token. Impacted is an unknown function of the component JSON Web Token Handler. Such manipulation leads to data authenticity. This vulnerability is documented as CVE-2023-48238. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in joaquimserafim json-web-token. Affected by this issue is an unknown function of the component JSON Web Token Handler. The manipulation with an unknown input leads to a data authenticity vulnerability. Using CWE to declare the problem leads to CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. Impacted is integrity. CVE summarizes:

joaquimserafim/json-web-token is a javascript library use to interact with JSON Web Tokens (JWT) which are a compact URL-safe means of representing claims to be transferred between two parties. Versions prior to 4.0.0 are vulnerable to a JWT algorithm confusion attack. On line 86 of the 'index.js' file, the algorithm to use for verifying the signature of the JWT token is taken from the JWT token, which at that point is still unverified and thus shouldn't be trusted. To exploit this vulnerability, an attacker needs to craft a malicious JWT token containing the HS256 algorithm, signed with the public RSA key of the victim application. This attack will only work against this library is the RS256 algorithm is in use, however it is a best practice to use that algorithm. Version 4.0.0 fixes the issue.

The weakness was released 11/18/2023 as GHSA-4xw9-cx39-r355. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2023-48238 since 11/13/2023. There are neither technical details nor an exploit publicly available.

Upgrading to version 3.1.1 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• joaquimserafim

Name

• json-web-token

Website

• Product: https://github.com/joaquimserafim/json-web-token/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion