Improper Enforcement of Message Integrity During Transmission in a Communication Channel Affecting minio-fips package, versions *


Severity

Recommended
0.0
medium
0
10

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

Threat Intelligence

EPSS
0.85% (54th 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-MINIMOSLATEST-MINIOFIPS-16309828
  • published28 Apr 2026
  • disclosed19 Mar 2021

Introduced: 19 Mar 2021

CVE-2021-21390  (opens in a new tab)
CWE-924  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest minio-fips.

NVD Description

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

MinIO is an open-source high performance object storage service and it is API compatible with Amazon S3 cloud storage service. In MinIO before version RELEASE.2021-03-17T02-33-02Z, there is a vulnerability which enables MITM modification of request bodies that are meant to have integrity guaranteed by chunk signatures. In a PUT request using aws-chunked encoding, MinIO ordinarily verifies signatures at the end of a chunk. This check can be skipped if the client sends a false chunk size that is much greater than the actual data sent: the server accepts and completes the request without ever reaching the end of the chunk + thereby without ever checking the chunk signature. This is fixed in version RELEASE.2021-03-17T02-33-02Z. As a workaround one can avoid using "aws-chunked" encoding-based chunk signature upload requests instead use TLS. MinIO SDKs automatically disable chunked encoding signature when the server endpoint is configured with TLS.

CVSS Base Scores

version 3.1