Use of a Broken or Risky Cryptographic Algorithm Affecting k3d package, versions <5.6.0-r11


Severity

Recommended
0.0
low
0
10

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

Threat Intelligence

EPSS
0.04% (15th 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 Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-WOLFILATEST-K3D-6593434
  • published9 Apr 2024
  • 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 Wolfi k3d to version 5.6.0-r11 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream k3d package and not the k3d package as distributed by Wolfi. See How to fix? for Wolfi 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 Scores

version 3.1