LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2975: AES-SIV implementation ignores empty associated data entries

Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence. Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be misled by removing, adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications. The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated. As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

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.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-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
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-2975Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenSSLOpenSSL3.1.0, 3.0.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-354 · source CWE mapping

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.