PT-2021-24401 · Unknown · Encryption Sdk
Published
2021-06-01
·
Updated
2021-06-01
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
Name of the Vulnerable Software and Affected Versions:
Encryption SDK versions prior to 1.9
Encryption SDK versions prior to 2.2
Description:
This issue concerns the Encryption SDK's handling of streaming signed messages and restricting processing of certain types of invalid messages. The SDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. Although the integrity of the ciphertext or decrypted plaintext is not impacted, some callers may rely on the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. The update introduces a new API for callers who wish to stream only unsigned messages and a new configuration to limit the number of Encrypted Data Keys (EDKs) that the SDK will attempt to process per message.
Recommendations:
For versions prior to 1.9, upgrade to version 1.9 or later to address these issues.
For versions prior to 2.2, upgrade to version 2.2 or later to address these issues.
Customers leveraging the SDK’s streaming features should ensure that client code reads to the end of the stream before using released plaintext.
Using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated.
Users processing SDK messages from untrusted sources should use the new maximum encrypted data keys parameter.
Improper Verification of Cryptographic Signature
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Encryption Sdk