CVE-2020-8912

Description

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.

CVSS Metrics

• v3.1•LOW•Score: 2.5CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
• v2.0•LOW•Score: 2.1AV:L/AC:L/Au:N/C:P/I:N/A:N

EPSS Trends

Current EPSS score: 0.23%• Percentile: 14%

Techniques & Countermeasures

• CWE-327•Use of a Broken or Risky Cryptographic Algorithm

  The product uses a broken or risky cryptographic algorithm or protocol.

Affected Systems

• amazon•aws_s3_crypto_sdk

  < 2.0

• chainguard•amazon-cloudwatch-agent

  < 0

• chainguard•amazon-cloudwatch-agent-fips

  < 0

• chainguard•amazon-ecs-agent

  < 0

• chainguard•amazon-ecs-agent-fips

  < 0

• chainguard•apply-cve-bump

  < 0

• chainguard•argo-cd-3.0

  < 3.0.23-r5

• chainguard•argo-cd-3.0-compat

  < 3.0.23-r5

• chainguard•argo-cd-3.1

  < 3.1.16-r3

• chainguard•argo-cd-3.1-compat

  < 3.1.16-r3

• chainguard•argo-cd-3.2

  < 0

• chainguard•argo-cd-3.2-compat

  < 0

• chainguard•argo-cd-3.3

  < 0

• chainguard•argo-cd-3.3-compat

  < 0

• chainguard•argo-cd-fips-3.0

  < 3.0.23-r6

• chainguard•argo-cd-fips-3.0-compat

  < 3.0.23-r6

• chainguard•argo-cd-fips-3.1

  < 3.1.16-r1

• chainguard•argo-cd-fips-3.1-compat

  < 3.1.16-r1

• chainguard•argo-cd-fips-3.2

  < 0

• chainguard•argo-cd-fips-3.2-compat

  < 0

• chainguard•argo-cd-fips-3.3

  < 0

• chainguard•argo-cd-fips-3.3-compat

  < 0

• chainguard•argo-events

  < 0

• chainguard•argo-events-fips

  < 0

• chainguard•argo-rollouts

  < 0

• chainguard•argo-rollouts-fips

  < 0

• chainguard•atlas-1.0

  < 0

• chainguard•atlas-1.0-fips

  < 0

• chainguard•atlas-1.1

  < 0

• chainguard•atlas-1.1-fips

  < 0

• chainguard•atlas-1.2

  < 0

• chainguard•aws-flb-cloudwatch

  < 0

• chainguard•aws-flb-cloudwatch-fips

  < 0

• chainguard•aws-flb-firehose

  < 0

• chainguard•aws-flb-firehose-fips

  < 0

• chainguard•aws-flb-kinesis

  < 0

• chainguard•aws-flb-kinesis-fips

  < 0

• chainguard•aws-node-termination-handler

  < 0

• chainguard•aws-node-termination-handler-fips

  < 0

• chainguard•aws-nuke

  < 0

• chainguard•aws-nuke-fips

  < 0

• chainguard•aws-otel-collector

  < 0

• chainguard•aws-otel-collector-fips

  < 0

• chainguard•aws-s3-controller

  < 0

• chainguard•aws-sigv4-proxy

  < 0

• chainguard•aws-sigv4-proxy-fips

  < 0

• chainguard•bank-vaults

  < 0

• chainguard•bank-vaults-fips

  < 0

• chainguard•bank-vaults-vault-operator

  < 0

• chainguard•bank-vaults-vault-operator-fips

  < 0

Showing first 50 affected entries in server-rendered view.

References (10)

• 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
• https://nvd.nist.gov/vuln/detail/CVE-2020-8912
• https://github.com/aws/aws-sdk-go/pull/3403
• https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e
• https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4
• https://bugzilla.redhat.com/show_bug.cgi?id=1869801
• https://github.com/aws/aws-sdk-go
• https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc
• https://pkg.go.dev/vuln/GO-2022-0646