OpenIDC cjose up to 0.6.2.1 Authentication Tag risky encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in OpenIDC cjose up to 0.6.2.1. The impacted element is an unknown function of the component Authentication Tag Handler. Performing a manipulation results in risky encryption. This vulnerability is cataloged as CVE-2023-37464. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in OpenIDC cjose up to 0.6.2.1. This affects some unknown processing of the component Authentication Tag Handler. The manipulation with an unknown input leads to a risky encryption vulnerability. CWE is classifying the issue as CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. This is going to have an impact on confidentiality. The summary by CVE is:
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).
The weakness was shared 07/15/2023 as GHSA-3rhg-3gf2-6xgj. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2023-37464 since 07/06/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
The vulnerability scanner Nessus provides a plugin with the ID 239737 (TencentOS Server 4: cjose (TSSA-2025:0135)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 0.6.2.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 7325e9a5e71e2fc0e350487ecac7d84acdf0ed5e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at Tenable (239737). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/OpenIDC/cjose/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 8.6
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Risky encryptionCWE: CWE-327 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 239737
Nessus Name: TencentOS Server 4: cjose (TSSA-2025:0135)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: cjose 0.6.2.2
Patch: 7325e9a5e71e2fc0e350487ecac7d84acdf0ed5e
Timeline
07/06/2023 🔍07/15/2023 🔍
07/15/2023 🔍
06/21/2025 🔍
Sources
Product: github.comAdvisory: GHSA-3rhg-3gf2-6xgj
Status: Confirmed
CVE: CVE-2023-37464 (🔍)
GCVE (CVE): GCVE-0-2023-37464
GCVE (VulDB): GCVE-100-234219
Entry
Created: 07/15/2023 06:20Updated: 06/21/2025 11:26
Changes: 07/15/2023 06:20 (54), 08/06/2023 08:40 (11), 06/21/2025 11:26 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.