Associated-data tampering via zero-length AES-SIV bypass
Published Jul 14, 2023 · Updated Apr 23, 2025
Integrity failure in OpenSSL 3.0.0 through 3.0.9 and 3.1.0 through 3.1.1 allows attackers to alter empty AES-SIV associated data via crafted calls. The AES-SIV cipher's siv_cipher path returns success for a zero-length EVP_EncryptUpdate or EVP_CipherUpdate call before authenticating associated data. Exploitation requires an application that separately authenticates empty associated-data entries; non-empty entries and the FIPS provider are unaffected.
Summary
What happened
Integrity failure in OpenSSL 3.0.0 through 3.0.9 and 3.1.0 through 3.1.1 allows attackers to alter empty AES-SIV associated data via crafted calls. The AES-SIV cipher's siv_cipher path returns success for a zero-length EVP_EncryptUpdate or EVP_CipherUpdate call before authenticating associated data. Exploitation requires an application that separately authenticates empty associated-data entries; non-empty entries and the FIPS provider are unaffected.
The record
- CVE
- CVE-2023-2975
- Published
- Jul 14, 2023
- Updated
- Apr 23, 2025
- Vendor
- OpenSSL Project
- Product
- OpenSSL
- Classifications
- CWE-354, T1565
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2023CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0 <3.0.10
- Affected versionversion=3.1.0 <3.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo