openssl/crypto/cms
Bernd Edlinger 5840ed0cd1 Fix a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey
An attack is simple, if the first CMS_recipientInfo is valid but the
second CMS_recipientInfo is chosen ciphertext. If the second
recipientInfo decodes to PKCS #1 v1.5 form plaintext, the correct
encryption key will be replaced by garbage, and the message cannot be
decoded, but if the RSA decryption fails, the correct encryption key is
used and the recipient will not notice the attack.

As a work around for this potential attack the length of the decrypted
key must be equal to the cipher default key length, in case the
certifiate is not given and all recipientInfo are tried out.

The old behaviour can be re-enabled in the CMS code by setting the
CMS_DEBUG_DECRYPT flag.

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9777)
2019-09-10 11:31:25 +01:00
..
build.info
cms_asn1.c
cms_att.c
cms_cd.c
cms_dd.c
cms_enc.c
cms_env.c Fix a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey 2019-09-10 11:31:25 +01:00
cms_err.c
cms_ess.c
cms_io.c
cms_kari.c
cms_lcl.h Fix a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey 2019-09-10 11:31:25 +01:00
cms_lib.c
cms_pwri.c
cms_sd.c Add the ability to perform signatures in a provider 2019-09-09 13:52:26 +01:00
cms_smime.c Fix a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey 2019-09-10 11:31:25 +01:00