CVE-2025-27414: MinIO SFTP authentication bypass due to improperly trusted SSH key

Published Feb 28, 2025
·
Updated

Summary A bug in evaluating the trust of the SSH key used in an SFTP connection to MinIO allows authentication bypass and unauthorized data access.

Details

On a MinIO server with SFTP access configured and using LDAP as an external identity provider, MinIO supports SSH key based authentication for SFTP connections when the user has the sshPublicKey attribute set in their LDAP server. The server trusts the client's key only when the public key is the same as the sshPublicKey attribute.

Due to the bug, when the user has no sshPublicKey property in LDAP, the server ends up trusting the key allowing the client to perform any FTP operations allowed by the MinIO access policies associated with the LDAP user (or any of their groups).

The bug was introduced in https://github.com/minio/minio/commit/91e1487de45720753c9e9e4c02b1bd16b7e452fa.

Impact

The following requirements must be met to exploit this vulnerability:

1. MinIO server must be configured to allow SFTP access and use LDAP as an external identity provider. 2. Knowledge of an LDAP username that does not have the sshPublicKey property set. 3. Such an LDAP username or one of their groups must also have some MinIO access policy configured.

When this bug is successfully exploited, the attacker can perform any FTP operations (i.e. reading, writing, deleting and listing objects) allowed by the access policy associated with the LDAP user account (and their groups).

Other sources

MinIO is a high performance object storage. Starting in RELEASE.2024-06-06T09-36-42Z and prior to RELEASE.2025-02-28T09-55-16Z, a bug in evaluating the trust of the SSH key used in an SFTP connection to MinIO allows authentication bypass and unauthorized data access. On a MinIO server with SFTP access configured and using LDAP as an external identity provider, MinIO supports SSH key based authentication for SFTP connections when the user has the sshPublicKey attribute set in their LDAP server. The server trusts the client's key only when the public key is the same as the sshPublicKey attribute. Due to the bug, when the user has no sshPublicKey property in LDAP, the server ends up trusting the key allowing the client to perform any FTP operations allowed by the MinIO access policies associated with the LDAP user (or any of their groups). Three requirements must be met in order to exploit the vulnerability. First, the MinIO server must be configured to allow SFTP access and use LDAP as an external identity provider. Second, the attacker must have knowledge of an LDAP username that does not have the sshPublicKey property set. Third, such an LDAP username or one of their groups must also have some MinIO access policy configured. When this bug is successfully exploited, the attacker can perform any FTP operations (i.e. reading, writing, deleting and listing objects) allowed by the access policy associated with the LDAP user account (and their groups). Version 1.2.0 fixes the issue.

MITRE

Affected Software

2 affected componentsFixes available
MinIO>=RELEASE.2024-06-06T09-36-42Z<RELEASE.2025-02-28T09-55-16Z
go/github.com/minio/minio>=0.0.0-20240605075113-91e1487de457<0.0.0-20250227184332-4c71f1b4ec0f
0.0.0-20250227184332-4c71f1b4ec0f

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/minio/minio to a version that resolves this vulnerability.

    Fixed in 0.0.0-20250227184332-4c71f1b4ec0f
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.2.0
  3. Configuration

    Ensure MinIO is configured to allow SFTP access and use LDAP as the external identity provider (as described in the advisory: this is the affected setup where SSH key trust is evaluated against LDAP).

    MinIO server SFTP access configuration = enabled
  4. Configuration

    Set the sshPublicKey attribute in LDAP for any LDAP username (or one of their groups) that also has MinIO access policies, since the bypass occurs when sshPublicKey is not set.

    LDAP user entries sshPublicKey attribute presence = set for all LDAP users/groups that have MinIO access policies

Event History

Feb 28, 2025
CVE Published
via MITRE·09:06 PM
Data Sourced
via MITRE·09:06 PM
DescriptionWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Mar 3, 2025
Advisory Published
via GitHub·07:56 PM
Nov 18, 57181
Event
via FIRST·05:55 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-27414?

The severity of CVE-2025-27414 is considered high due to the potential for authentication bypass and unauthorized data access.

2

How do I fix CVE-2025-27414?

To fix CVE-2025-27414, upgrade MinIO to a version released after RELEASE.2025-02-28T09-55-16Z.

3

What systems are affected by CVE-2025-27414?

CVE-2025-27414 affects MinIO versions from RELEASE.2024-06-06T09-36-42Z to RELEASE.2025-02-28T09-55-16Z.

4

What vulnerability does CVE-2025-27414 address?

CVE-2025-27414 addresses a vulnerability that allows for authentication bypass through improper evaluation of SSH keys in SFTP connections.

5

Can CVE-2025-27414 lead to data breaches?

Yes, CVE-2025-27414 can lead to data breaches as it allows unauthorized access to sensitive data on MinIO servers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203