Loading vulnerability…
A high-severity buffer overflow vulnerability in OpenSSL’s SM2 decryption implementation affects the EVP_PKEY_decrypt() API in OpenSSL 1.1.1 through 1.1.1k. During the common two-call usage pattern for EVP_PKEY_decrypt(), the first call is used to determine the required plaintext buffer length and the second call performs the actual decryption into an application-supplied buffer. Due to a flaw in the SM2 decryption code, the size reported by the first call can be smaller than the amount of plaintext written by the second call. If an application allocates its output buffer based on the underestimated length, attacker-controlled SM2 ciphertext can trigger a write past the end of that buffer. The overflow is reported as up to 62 bytes and typically affects heap-allocated memory adjacent to the plaintext buffer. This can corrupt nearby application data, alter program behavior, or terminate the process.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An OpenSSL vulnerability mentioned only in related content, not part of the main article.
A high-severity buffer overflow in OpenSSL's SM2 decryption implementation where EVP_PKEY_decrypt() may underestimate the required plaintext buffer size, enabling overflow of attacker-controlled data by up to 62 bytes and potentially causing crashes or altered application behavior.
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.