github.com/aws/aws-sdk-go
Activity
- Latest release
- 1y ago
- Total releases
- 69
- Cadence
- ~16 days
- Last 12 months
- 0
Reach
- Stars
- —
Details
- First release
- Oct 01, 2015
| Version | Released | |
|---|---|---|
v1.55.8
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.8
patch
Dependencies (1)
|
|
v1.55.7
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.7
patch
Dependencies (1)
|
|
v1.55.6
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.6
patch
Dependencies (1)
|
|
v1.55.5
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.5
patch
Dependencies (1)
|
|
v1.55.4
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.4
patch
Dependencies (1)
|
|
v1.55.3
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.3
patch
Dependencies (1)
|
|
v1.55.2
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.2
patch
Dependencies (1)
|
|
v1.55.1
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.1
patch
Dependencies (1)
|
|
v1.55.0
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.55.0
minor
Dependencies (1)
|
|
v1.54.20
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.20
patch
Dependencies (1)
|
|
v1.54.19
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.19
patch
Dependencies (1)
|
|
v1.54.18
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.18
patch
Dependencies (1)
|
|
v1.54.17
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.17
patch
Dependencies (1)
|
|
v1.54.16
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.16
patch
Dependencies (1)
|
|
v1.54.15
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.15
patch
Dependencies (1)
|
|
v1.54.14
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.14
patch
Dependencies (1)
|
|
v1.54.13
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.13
patch
Dependencies (1)
|
|
v1.54.12
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.12
patch
Dependencies (1)
|
|
v1.54.11
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.11
patch
Dependencies (1)
|
|
v1.54.10
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.10
patch
Dependencies (1)
|
|
v1.54.1
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.54.1
minor
Dependencies (2)
|
|
v1.52.3
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.52.3
minor
Dependencies (2)
|
|
v1.51.17
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.51.17
patch
Dependencies (2)
|
|
v1.51.9
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.51.9
minor
Dependencies (2)
|
|
v1.44.288
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.288
patch
Dependencies (3)
|
|
v1.44.275
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.275
patch
Dependencies (3)
|
|
v1.44.225
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.225
patch
Dependencies (3)
|
|
v1.44.206
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.206
patch
Dependencies (3)
|
|
v1.44.126
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.126
patch
Dependencies (3)
|
|
v1.44.89
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.89
patch
Dependencies (3)
|
|
v1.44.50
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.50
patch
Dependencies (3)
|
|
v1.44.48
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.48
patch
Dependencies (3)
|
|
v1.44.39
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.44.39
minor
Dependencies (3)
|
|
v1.43.13
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.43.13
patch
Dependencies (3)
|
|
v1.43.1
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.43.1
minor
Dependencies (3)
|
|
v1.42.35
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.42.35
patch
Dependencies (3)
|
|
v1.42.10
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.42.10
minor
Dependencies (3)
|
|
v1.40.57
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.40.57
patch
Dependencies (3)
|
|
v1.40.31
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.40.31
patch
Dependencies (3)
|
|
v1.40.19
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.40.19
patch
Dependencies (3)
|
|
v1.40.18
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.40.18
minor
Dependencies (3)
|
|
v1.38.6
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.38.6
minor
Dependencies (3)
|
|
v1.37.11
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.37.11
minor
Dependencies (3)
|
|
v1.36.20
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.36.20
minor
Dependencies (3)
|
|
v1.35.12
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.35.12
patch
Dependencies (3)
|
|
v1.35.11
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.35.11
patch
Dependencies (3)
|
|
v1.35.9
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.35.9
minor
Dependencies (3)
|
|
v1.34.20
patch
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.34.20
patch
Dependencies (4)
|
|
v1.34.10
minor
1 CVE
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev |
v1.34.10
minor
Dependencies (4)
|
|
v1.30.27
minor
3 CVEs
CVE-2020-8912
GO-2022-0635
GHSA-7f33-f4f5-xwgw
Dec 12, 2024
In-band key negotiation issue in AWS S3 Crypto SDK for golang in github.com/aws/aws-sdk-go 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. It is recommended to update your SDK to V2 or later, and re-encrypt your files. References
Updated Feb 04, 2026 · Source: OSV.dev
CVE-2022-2582
GHSA-6jvc-q2x7-pchv
GHSA-76wf-9vgp-pj7w
GO-2022-0391
Dec 28, 2022
AWS S3 Crypto SDK sends an unencrypted hash of the plaintext alongside the ciphertext as a metadata field
4.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
None
None
The AWS S3 Crypto SDK sends an unencrypted hash of the plaintext alongside the ciphertext as a metadata field. This hash can be used to brute force the plaintext, if the hash is readable to the attacker. AWS now blocks this metadata field, but older SDK versions still send it. Fixed in
1.34.0
References Updated Sep 10, 2026 · Source: OSV.dev
CVE-2020-8911
GHSA-f5pg-7wfw-84q9
GO-2022-0646
Feb 11, 2022
CBC padding oracle issue in AWS S3 Crypto SDK for golang
5.6
/ 10
Medium
Local
High
Low
None
Changed
High
None
None
SummaryThe golang AWS S3 Crypto SDK is impacted by an issue that can result in loss of confidentiality and message forgery. The attack requires write access to the bucket in question, and that the attacker has access to an endpoint that reveals decryption failures (without revealing the plaintext) and that when encrypting the CBC option was chosen as content cipher. Risk/SeverityThe vulnerability pose insider risks/privilege escalation risks, circumventing KMS controls for stored data. ImpactThis advisory describes the plaintext revealing vulnerabilities in the golang AWS S3 Crypto SDK, with a similar issue in the non "strict" versions of C++ and Java S3 Crypto SDKs being present as well. V1 prior to 1.34.0 of the S3 crypto SDK, allows users to encrypt files with AES-CBC, without computing a MAC on the data. Note that there is an alternative option of using AES-GCM, which is used in the examples of the documentation and not affected by this vulnerability, but by CVE-2020-8912. This exposes a padding oracle vulnerability: If the attacker has write access to the S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file (without observing the file contents that the endpoint learns in the process), they can reconstruct the plaintext with (on average) This issue is fixed in V2 of the API, by disabling encryption with CBC mode for new files. Old files, if they have been encrypted with CBC mode, remain vulnerable until they are reencrypted with AES-GCM. MitigationUsing the version 2 of the S3 crypto SDK will not produce vulnerable files anymore. Old files remain vulnerable to this problem if they were originally encrypted with CBC mode. Proof of conceptA Proof of concept is available in a separate github repository. This particular issue is described in padding_oracle_exploit.go:
Fixed in
1.34.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
v1.30.27
minor
Dependencies (4)
|