Skip to content

Rancher allows an unauthenticated stack overflow in /v3-public/authproviders API

High severity GitHub Reviewed Published Feb 27, 2025 in rancher/rancher • Updated Feb 27, 2025

Package

gomod github.com/rancher/rancher (Go)

Affected versions

>= 2.8.0, < 2.8.13
>= 2.9.0, < 2.9.7
>= 2.10.0, < 2.10.3

Patched versions

2.8.13
2.9.7
2.10.3

Description

Impact

An unauthenticated stack overflow crash, leading to a denial of service (DoS), was identified in Rancher’s /v3-public/authproviders public API endpoint. A malicious user could submit data to the API which would cause the Rancher server to crash, but no malicious or incorrect data would actually be written in the API. The downstream clusters, i.e., the clusters managed by Rancher, are not affected by this issue.

This vulnerability affects those using external authentication providers as well as Rancher’s local authentication.

Patches

The patch includes the removal of unnecessary HTTP methods of the specific API.

Patched versions include releases v2.8.13, v2.9.7 and v2.10.3.

Workarounds

There are no workarounds for this issue. Users are recommended to upgrade, as soon as possible, to a version of Rancher Manager that contains the fix.

References

If you have any questions or comments about this advisory:

References

@pdellamore pdellamore published to rancher/rancher Feb 27, 2025
Published to the GitHub Advisory Database Feb 27, 2025
Reviewed Feb 27, 2025
Last updated Feb 27, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

EPSS score

Weaknesses

CVE ID

CVE-2025-23388

GHSA ID

GHSA-xr9q-h9c7-xw8q

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.