Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2020-8911

MEDIUM

CVE-2020-8911 is a medium-severity (CVSS 5.6) Broken Cryptographic Algorithm vulnerability in amazon aws s3 crypto sdk. 1 public exploit reference exists, so weaponization risk is real. O3 Security detects and blocks CVE-2020-8911 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

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…

Published
Aug 11, 2020
Updated
Jun 17, 2026
Affected
0 pkgs
Patched
None yet
Exploits
1 known

Description

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. It is recommended to update your SDK to V2 or later, and re-encrypt your files.

Affected Products

1 product · 1 configurations
Application
aws s3 crypto sdkamazon
< 2.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every amazon aws s3 crypto sdk deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Fix

    Apply the amazon aws s3 crypto sdk security patch or hotfix for CVE-2020-8911 on the affected version, following the vendor advisory for your exact build.

  3. Workarounds

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2020-8911 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2020-8911. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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. It is recommended to update your SDK t
O3 Security · Runtime Protection

Is CVE-2020-8911 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2020-8911 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.