minio up to RELEASE.2025-02-28T09-55-16Z signature verification

Summaryinfo

A vulnerability identified as problematic has been detected in minio. The impacted element is an unknown function. This manipulation causes signature verification. This vulnerability is tracked as CVE-2025-31489. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in minio and classified as problematic. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a signature verification vulnerability. The CWE definition for the vulnerability is CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. As an impact it is known to affect integrity. The summary by CVE is:

MinIO is a High Performance Object Storage released under GNU Affero General Public License v3.0. The signature component of the authorization may be invalid, which would mean that as a client you can use any arbitrary secret to upload objects given the user already has prior WRITE permissions on the bucket. Prior knowledge of access-key, and bucket name this user might have access to - and an access-key with a WRITE permissions is necessary. However with relevant information in place, uploading random objects to buckets is trivial and easy via curl. This issue is fixed in RELEASE.2025-04-03T14-56-28Z.

The advisory is shared at github.com. This vulnerability is known as CVE-2025-31489 since 03/28/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

Upgrading to version RELEASE.2025-04-03T14-56-28Z eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• minio

Version

• 0.12.3
• 2021-01-30T00-20-58Z
• 2021-03-17T02-33-02Z
• 2021-10-10T16-53-30Z
• 2021-10-13T00-23-17Z
• 2022-04-12T06-55-35Z
• 2023-03-20T20-16-18Z
• <=0.12.2
• <=2022-06-02T02-11-04Z
• RELEASE.2020-04-23T00-58-49Z
• RELEASE.2021-03-04T00-53-13Z
• RELEASE.2021-12-27T07-23-18Z
• RELEASE.2024-01-31T20-20-33Z
• RELEASE.2024-05-27T19-17-46Z
• RELEASE.2024-12-13T22-19-12Z
• RELEASE.2025-02-28T09-55-16Z

Website

• Product: https://github.com/minio/minio/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion