Defenders should note that the implementation reveals distinct error messages and timing discrepancies based on whether the decryption process fails due to padding, key size mismatch, or invalid padding bytes. These side channels function as a Bleichenbacher oracle. An attacker providing untrusted EnvelopedData to a service that automatically processes and reflects these decryption outcomes (such as an S/MIME gateway or automated mail filter) can iteratively recover the content-encryption key. This is caused by a failure to comply with RFC 3218 recommendations for constant-time failure handling and uniform error responses.

Impact

Successful exploitation allows for the recovery of content-encryption keys used in PKCS#7 protected data. This vulnerability affects any environment utilizing the cryptography library version 44.0.0 to 49.x.x to process untrusted S/MIME or EnvelopedData content. The impact is significant for secure messaging gateways and automated data processing pipelines that interact with external, potentially malicious, encrypted payloads.

Recommendation

• Update the cryptography library to version 50.0.0 or later immediately to implement RFC 3218-compliant constant-time decryption and uniform error reporting.
• Audit applications utilizing cryptography to determine if they automatically decrypt and reflect errors or processing results of untrusted EnvelopedData to external entities.
• Restrict the ability of automated systems to process untrusted EnvelopedData until the library patch is applied to mitigate the risk of automated oracle queries.