Use of a Broken or Risky Cryptographic Algorithm Affecting kots package, versions <1.130.6-r0


Severity

Recommended
0.0
low
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.23% (14th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-KOTS-17801948
  • published3 Jul 2026
  • disclosed11 Aug 2020

Introduced: 11 Aug 2020

CVE-2020-8912  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade Chainguard kots to version 1.130.6-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kots package and not the kots package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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 Base Scores

version 3.1