GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSL: SM2 decryption understates the required buffer, overflowing it by up to 62 bytes

CVSS 9.8CVE-2021-3711Kernel, userspace & hypervisorcurated

Impact

The SM2 decryption path reports a plaintext buffer size smaller than what the second EVP_PKEY_decrypt() call actually writes, so an application that follows the documented two-call pattern overflows its own buffer - usually on the heap - by up to 62 attacker-chosen bytes. Consequences range from corrupting adjacent application state to a crash, and the precise effect depends on the calling program. The practical caveat for a fleet is that only code paths that decrypt SM2 content from an untrusted party are reachable; most Western datacenter deployments never exercise SM2, so for them this is a library version to roll forward rather than an exposed path. Fixed in OpenSSL 1.1.1l; 1.1.1 through 1.1.1k are affected.

Who can reach it

An attacker who can present SM2-encrypted content to an application that calls EVP_PKEY_decrypt() on it with a caller-sized buffer. Reachability depends entirely on whether the service accepts SM2 input; authentication requirements are whatever the calling service imposes.

What to do

Update the distribution OpenSSL package to 1.1.1l or the vendor backport, then restart every service linked against the shared library - in practice a rolling daemon restart across the fleet, or a reboot if you would rather not chase every long-lived process. Statically linked appliances and vendor stacks (Siemens and NetApp advisories are in the record) need their own vendor update. No action is needed for images already on OpenSSL 3.x or 1.1.1l+.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.