What is the CVSS score of CVE-2020-8912?

CVE-2020-8912 has a CVSS 3.1 base score of 2.5 (Low). CVSS vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2020-8912?

Yes, a public proof-of-concept exploit is available for CVE-2020-8912. Prioritise patching immediately. EPSS: 0.2%.

Is there a patch available for CVE-2020-8912?

Yes, a patch is available for CVE-2020-8912. Update the affected software to the latest version immediately.

Amazon CVE-2020-8912

LOW

Use of a Broken or Risky Cryptographic Algorithm (CWE-327)

2020-08-11 cve-coordination@google.com

Information Disclosure Oracle Amazon Aws S3 Crypto Sdk

2.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

2.5 LOW

AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Aug 11, 2020 - 20:15 nvd

LOW 2.5

DescriptionNVD

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.

AnalysisAI

A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. Rated low severity (CVSS 2.5). Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-327. 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. Affected products include: Amazon Aws S3 Crypto Sdk.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.