Security readout for executives and security teams
Plain-English summary
OpenSSL’s AES-SIV mode can fail to authenticate empty associated-data entries. Only applications that rely on empty associated data as a security boundary are exposed. OpenSSL states it is unaware of affected applications and rates the issue low severity.
Executive priority
Handle through normal patch governance unless the organization has custom AES-SIV cryptographic workflows. Escalate only where empty associated data is part of integrity enforcement.
Technical view
In OpenSSL 3.1.0 and 3.0.0, AES-SIV returns success for zero-length associated-data update calls instead of authenticating them. Empty entries can be removed, added, or reordered without detection, creating a limited integrity issue under rare usage patterns.
Likely exposure
Exposure is likely narrow: systems must use OpenSSL AES-SIV and intentionally authenticate empty associated-data entries. Ordinary TLS usage is not identified as affected in the provided sources.
Exploitation context
The bundle reports KEV=false, and no cited source claims active exploitation. The practical attack surface appears application-specific and depends on security logic that treats empty associated-data entries as meaningful.
Researcher notes
The key condition is zero-length associated data passed with a null output buffer through EVP_EncryptUpdate or EVP_CipherUpdate. Non-empty associated data authentication is not reported affected.
Mitigation direction
- Upgrade OpenSSL 3.1 deployments to a release containing the 3.1.2 fix.
- Upgrade OpenSSL 3.0 deployments to a release containing the 3.0.10 fix.
- Review vendor advisories for packaged or embedded OpenSSL dependencies.
- Prioritize custom cryptographic applications using AES-SIV associated data.
Validation and detection
- Inventory OpenSSL versions and identify 3.1.0 or 3.0.0 usage.
- Search application code for AES-SIV use through EVP cipher APIs.
- Confirm whether empty associated-data entries are security-relevant.
- Verify deployed packages include the referenced OpenSSL patch commits.
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-354: 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-2975 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
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- OpenSSL AdvisoryCVE reference · vendor-advisory
- 3.1.2 git commitCVE reference · patch
- 3.0.10 git commitCVE reference · patch
- https://security.netapp.com/advisory/ntap-20230725-0004/CVE reference · x_transferred
- https://security.gentoo.org/glsa/202402-08CVE reference · x_transferred
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.
Improper Validation of Integrity Check Value
Improper Validation of Integrity Check Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
