Vendordebian, netapp, oracle, opensslProductdebian linux, clustered data ontap, active iq unified manager, oncommand insight, oncommand workflow automation, snapcenter, e-series santricity os controller, jd edwards enterpriseone tools, communications session border controller, enterprise communications broker, solidfire, openssl, hci management node, santricity smi-s provider, mysql connectors, clustered data ontap antivirus connector, communications cloud native core unified data repository, essbase, communications cloud native core security edge protection proxy, jd edwards world security, manageability software development kit, enterprise session border controller, storage encryption, communications unified session manager, health sciences inform publisherDiscoveredAug 24, 2021UpdatedNov 21, 2024
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when…