aws-encryption-sdk-cli@1.1.4 vulnerabilities
This command line tool can be used to encrypt and decrypt files and directories using the AWS Encryption SDK.
-
latest version
4.1.0
-
latest non vulnerable version
-
first published
6 years ago
-
latest version published
3 years ago
-
licenses detected
- [0,)
Direct Vulnerabilities
Known vulnerabilities in the aws-encryption-sdk-cli package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.| Vulnerability | Vulnerable Version |
|---|---|
aws-encryption-sdk-cli is a This command line tool can be used to encrypt and decrypt files and directories using the AWS Encryption SDK. Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature. The ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the 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 How to fix Improper Verification of Cryptographic Signature? Upgrade |
[2.0.0,2.2.0)
[,1.9.0)
|
aws-encryption-sdk-cli is a This command line tool can be used to encrypt and decrypt files and directories using the AWS Encryption SDK. Affected versions of this package are vulnerable to Insecure Permissions. In the affected versions, the AWS Encryption CLI operated in "discovery mode" even when "strict mode" was specified. Although decryption only succeeded if the user had permission to decrypt with at least one of the CMKs, decryption could be successful using a CMK that was not included in the user-defined set when the CLI was operating in "strict mode". How to fix Insecure Permissions? Upgrade |
[,1.8.0)
[2.0.0,2.1.0)
|