CVE-2023-2975 is a low-severity flaw in the OpenSSL AES-SIV cipher implementation. In affected releases, an attempt to add an empty associated-data entry through EVP_EncryptUpdate() or EVP_CipherUpdate()—using a NULL output buffer and zero input length—returns success without incorporating that entry into AES-SIV authentication. Consequently, empty associated-data entries are omitted from the authenticated data vector, whereas non-empty associated data is processed correctly. Affected versions are OpenSSL 3.0.0 through 3.0.9 and 3.1.0 through 3.1.1. OpenSSL 1.0.2 and 1.1.1 are unaffected; the FIPS provider is also unaffected because it does not implement AES-SIV.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An OpenSSL AES-SIV vulnerability related to improper handling of empty associated data entries.
Unknown
A vulnerability addressed by the updated Red Hat Developer Hub container image; no technical details are provided in this advisory text.
A Linux kernel CVE addressed by the advisory; no further description is provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.