First published: Tue Aug 18 2020(Updated: )
A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. Reference: <a href="https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09">https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09</a> <a href="https://github.com/google/security-research/security/advisories/GHSA-f5pg-7wfw-84q9">https://github.com/google/security-research/security/advisories/GHSA-f5pg-7wfw-84q9</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Amazon Simple Storage Service | <V2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1869800 is high due to the potential for attackers to exploit the padding oracle vulnerability.
To fix REDHAT-BUG-1869800, update to AWS S3 Crypto SDK for GoLang version V2 or later.
REDHAT-BUG-1869800 affects AWS S3 Crypto SDK for GoLang versions prior to V2.
A padding oracle vulnerability in REDHAT-BUG-1869800 allows attackers to exploit the encryption mechanism by manipulating encrypted data without proper authentication.
Yes, an attacker with write access to the S3 bucket can exploit REDHAT-BUG-1869800 remotely if the target is using an affected version.