Security readout for executives and security teams
Plain-English summary
cjose can accept an incorrectly shortened AES-GCM authentication tag when decrypting encrypted JOSE data. That weakens integrity protection: a remote unauthenticated attacker may be able to alter protected JWE content. Organizations using cjose before 0.6.2.2 should treat this as a high-priority library exposure.
Executive priority
Prioritize remediation where cjose protects authentication, authorization, session, or inter-service security data. The business risk is altered encrypted security tokens or messages, not data theft by itself, based on the cited impact.
Technical view
OpenIDC/cjose versions before 0.6.2.2 use the tag length supplied in the JWE authentication tag instead of enforcing the RFC-required 16 octets for AES-GCM. The advisory says this permits truncated tags and corresponding JWE modification. CVSS is 8.6 with high integrity impact.
Likely exposure
Exposure is most likely in applications, services, or OS packages that link against OpenIDC/cjose and process encrypted JWE data using AES-GCM. Debian and Fedora advisories indicate downstream packaged exposure existed.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is network-reachable, requires no privileges or user interaction, and affects integrity rather than confidentiality or availability.
Researcher notes
Key evidence is the OpenIDC advisory, the fixing commit, and RFC 7518 section 4.7 requiring a 128-bit authentication tag for AES-GCM content encryption. Evidence is strong for affected version and fix, but public exploit status is not established in the bundle.
Mitigation direction
- Upgrade OpenIDC/cjose to version 0.6.2.2 or later.
- Apply Debian or Fedora security updates where cjose is installed from packages.
- If upgrade is blocked, avoid AES-GCM encryption in cjose-backed JWE flows.
- Use an alternative encryption algorithm named by vendor guidance, such as AES-CBC.
- Monitor OpenIDC and distribution advisories for packaging-specific remediation details.
Validation and detection
- Inventory applications and containers for OpenIDC/cjose library usage.
- Check installed cjose versions and confirm they are 0.6.2.2 or later.
- Identify JWE processing paths that use AES-GCM with cjose.
- Confirm downstream OS packages include the vendor security fix.
- Add regression tests that reject non-16-octet AES-GCM authentication tags.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-37464 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N3.94Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/OpenIDC/cjose/security/advisories/GHSA-3rhg-3gf2-6xgjCVE reference · x_refsource_CONFIRM
- https://github.com/OpenIDC/cjose/commit/7325e9a5e71e2fc0e350487ecac7d84acdf0ed5eCVE reference · x_refsource_MISC
- https://datatracker.ietf.org/doc/html/rfc7518#section-4.7CVE reference · x_refsource_MISC
- https://github.com/OpenIDC/cjose/releases/tag/v0.6.2.2CVE reference · x_refsource_MISC
- https://lists.debian.org/debian-lts-announce/2023/08/msg00002.htmlCVE reference
- https://www.debian.org/security/2023/dsa-5472CVE reference
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DFWAPMYYVBO2U65HPYDTBEKNSXG4TP5C/CVE reference
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PTZHOVGY7AHGNMEY245HK4Q36AMA53AL/CVE reference
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LCQJXKDPCWCXB2V4JMQ3UWYJ4UIBPUW6/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.