Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'

CVSS 3.1 7.2 HIGHCVSS 4.0 8.6 HIGHEUVD CVSS 4.0 8.6 CVSS 4.0 · [email protected] · Secondary 8.6 HIGHCVSS 3.1 · [email protected] · Secondary 7.2 HIGHCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by github.com/rancher/rancher 2.6.14Fixed by github.com/rancher/rancher 2.7.10Fixed by github.com/rancher/rancher 2.8.2osv · severity unknownKEV status unknown

cve-program · CVE-2023-32194

Published

A vulnerability has been identified when granting a create or * global role for a resource type of "namespaces"; no matter the API group, the subject will receive * permissions for core namespaces. This can lead to someone being capable of accessing, creating, updating, or deleting a namespace in the project.

Read the publisher's advisory

euvd · EUVD-2024-0611

Published

A vulnerability has been identified when granting a create or * global role for a resource type of "namespaces"; no matter the API group, the subject will receive * permissions for core namespaces. This can lead to someone being capable of accessing, creating, updating, or deleting a namespace in the project.

Read the publisher's advisory

nvd · CVE-2023-32194

Published

A vulnerability has been identified when granting a create or * global role for a resource type of "namespaces"; no matter the API group, the subject will receive * permissions for core namespaces. This can lead to someone being capable of accessing, creating, updating, or deleting a namespace in the project.

Read the publisher's advisory

osv · GHSA-c85r-fwc7-45vc

Published

### Impact A vulnerability has been identified when granting a `create` or `*` **global role** for a resource type of "namespaces"; no matter the API group, the subject will receive `*` permissions for core namespaces. This can lead to someone being capable of accessing, creating, updating, or deleting a namespace in the project. This includes reading or updating a namespace in the project so that it is available in other projects in which the user has the "manage-namespaces" permission or updating another namespace in which the user has normal "update" permissions to be moved into the project. The expected behavior is to not be able to create, update, or delete a namespace in the project or move another namespace into the project since the user doesn't have any permissions on namespaces in the core API group. Moving a namespace to another project could lead to leakage of secrets, in case the targeted project has secrets. And also can lead to the namespace being able to abuse the resource quotas of the targeted project. ### Patches Patched versions include releases `2.6.14`, `2.7.10` and `2.8.2`. ### Workarounds There is no direct mitigation besides updating Rancher to a patched version. ### References If you have any questions or comments about this advisory: - Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security-related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

Read the publisher's advisory

osv · GO-2024-2535

Published

Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core' in github.com/rancher/rancher. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/rancher/rancher from v2.6.0 before v2.6.14, from v2.7.0 before v2.7.10, from v2.8.0 before v2.8.2.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2023-32194

Published

github.com/rancher/rancher

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "defaultStatus": "unaffected",
                    "packageName": "github.com/rancher/rancher",
                    "product": "rancher",
                    "vendor": "SUSE",
                    "versions": [
                        {
                            "lessThan": "2.6.14",
                            "status": "affected",
                            "version": "2.6.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "2.7.10",
                            "status": "affected",
                            "version": "2.7.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "2.8.2",
                            "status": "affected",
                            "version": "2.8.0",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-0611

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 16, 2024, 12:56:37 PM

dateUpdated: Oct 16, 2024, 5:25:32 PM

1 related source bulletins · separate from aliases

WID-SEC-W-2024-0332: Rancher: Mehrere Schwachstellen

CVE-2023-22649 · CVE-2023-32193 · CVE-2023-32192 · CVE-2023-32194

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2023-32194

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-269

Original publisher date fields

published: 2024-10-16T13:15:12.787

lastModified: 2026-06-17T05:58:17.493

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-c85r-fwc7-45vc

Published

github.com/rancher/rancher

Go

SEMVER · introduced 2.6.0 → fixed 2.6.14

github.com/rancher/rancher

Go

SEMVER · introduced 2.7.0 → fixed 2.7.10

github.com/rancher/rancher

Go

SEMVER · introduced 2.8.0 → fixed 2.8.2

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2024-2535

Published

github.com/rancher/rancher

Go

SEMVER · introduced 0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 15:59 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current