Memory corruption via incorrect SM2 plaintext sizing
Published Aug 24, 2021 · Updated Sep 16, 2024
Heap buffer overflow in OpenSSL 1.1.1 through 1.1.1k allows remote attackers to corrupt memory via crafted SM2 ciphertext. The sm2_plaintext_size routine subtracts assumed fixed ASN.1 overhead from ciphertext length, so its first EVP_PKEY_decrypt call can report a buffer up to 62 bytes too small. Exploitation requires an application to decrypt attacker-controlled SM2 content with the two-call API pattern, allowing adjacent heap data changes or an application crash.
Summary
What happened
Heap buffer overflow in OpenSSL 1.1.1 through 1.1.1k allows remote attackers to corrupt memory via crafted SM2 ciphertext. The sm2_plaintext_size routine subtracts assumed fixed ASN.1 overhead from ciphertext length, so its first EVP_PKEY_decrypt call can report a buffer up to 62 bytes too small. Exploitation requires an application to decrypt attacker-controlled SM2 content with the two-call API pattern, allowing adjacent heap data changes or an application crash.
The record
- CVE
- CVE-2021-3711
- Published
- Aug 24, 2021
- Updated
- Sep 16, 2024
- Vendor
- OpenSSL Project
- Product
- OpenSSL
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k)
What conditions does exploitation require?
What is affected?
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