Use of a Broken or Risky Cryptographic Algorithm Affecting cjose-devel package, versions <0:0.6.1-3.module+el8.8.0+1406+4a7f5371


Severity

Recommended
0.0
high
0
10

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.2% (58th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-ROCKY8-CJOSEDEVEL-5829330
  • published9 Aug 2023
  • disclosed14 Jul 2023

Introduced: 14 Jul 2023

CVE-2023-37464  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:8 cjose-devel to version 0:0.6.1-3.module+el8.8.0+1406+4a7f5371 or higher.
This issue was patched in RLSA-2023:4418.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cjose-devel package and not the cjose-devel package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:8 relevant fixed versions and status.

OpenIDC/cjose is a C library implementing the Javascript Object Signing and Encryption (JOSE). The AES GCM decryption routine incorrectly uses the Tag length from the actual Authentication Tag provided in the JWE. The spec says that a fixed length of 16 octets must be applied. Therefore this bug allows an attacker to provide a truncated Authentication Tag and to modify the JWE accordingly. Users should upgrade to a version >= 0.6.2.2. Users unable to upgrade should avoid using AES GCM encryption and replace it with another encryption algorithm (e.g. AES CBC).

CVSS Scores

version 3.1