Use of a Broken or Risky Cryptographic Algorithm Affecting traefik-3 package, versions <3.3.5-r0


Severity

Recommended
0.0
medium
0
10

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

Threat Intelligence

EPSS
0.2% (43rd 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-MINIMOSLATEST-TRAEFIK3-17210249
  • published6 Jun 2026
  • disclosed11 Aug 2020

Introduced: 11 Aug 2020

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

How to fix?

Upgrade Minimos:latest traefik-3 to version 3.3.5-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream traefik-3 package and not the traefik-3 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1