REDHAT-BUG-1869801: Low severity amazon simple storage service vulnerability
A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-CTR. Using this in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation.
References:
https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09 https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-1869801?
REDHAT-BUG-1869801 has a critical severity rating due to the potential for unauthorized encryption algorithm changes in AWS S3 objects.
How do I fix REDHAT-BUG-1869801?
To fix REDHAT-BUG-1869801, upgrade to AWS S3 Crypto SDK for GoLang version 2 or higher.
Who is affected by REDHAT-BUG-1869801?
AWS S3 Crypto SDK for GoLang users prior to version 2 are affected by REDHAT-BUG-1869801.
What does REDHAT-BUG-1869801 exploit?
REDHAT-BUG-1869801 exploits the in-band key negotiation, allowing attackers with write access to change the encryption algorithm.
What are the implications of REDHAT-BUG-1869801?
The implications of REDHAT-BUG-1869801 include potential data exposure and integrity issues due to unauthorized encryption changes.