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 agents can be hijacked by taking over the Rancher Server URL

CVSS 3.1 8.0 HIGHEUVD CVSS 3.1 8.0 CVSS 3.1 · [email protected] · Secondary 8.0 HIGHCVSS_V3 Publisher rating HIGHFixed by github.com/rancher/rancher 2.7.15Fixed by github.com/rancher/rancher 2.8.8Fixed by github.com/rancher/rancher 2.9.2osv · severity unknownKEV status unknown

cve-program · CVE-2024-22030

Published

A vulnerability has been identified within Rancher that can be exploited in narrow circumstances through a man-in-the-middle (MITM) attack. An attacker would need to have control of an expired domain or execute a DNS spoofing/hijacking attack against the domain to exploit this vulnerability. The targeted domain is the one used as the Rancher URL.

Read the publisher's advisory

euvd · EUVD-2024-2807

Published

A vulnerability has been identified within Rancher that can be exploited in narrow circumstances through a man-in-the-middle (MITM) attack. An attacker would need to have control of an expired domain or execute a DNS spoofing/hijacking attack against the domain to exploit this vulnerability. The targeted domain is the one used as the Rancher URL.

Read the publisher's advisory

nvd · CVE-2024-22030

Published

A vulnerability has been identified within Rancher that can be exploited in narrow circumstances through a man-in-the-middle (MITM) attack. An attacker would need to have control of an expired domain or execute a DNS spoofing/hijacking attack against the domain to exploit this vulnerability. The targeted domain is the one used as the Rancher URL.

Read the publisher's advisory

osv · GHSA-h4h5-9833-v2p4

Published

### Impact A vulnerability has been identified within Rancher that can be exploited in narrow circumstances through a man-in-the-middle (MITM) attack. An attacker would need to have control of an expired domain or execute a DNS spoofing/hijacking attack against the domain to exploit this vulnerability. The targeted domain is the one used as the Rancher URL. SUSE is unaware of any successful exploitation of this vulnerability, which has a high complexity bar. Please consult the associated [MITRE ATT&CK - Technique - Adversary-in-the-Middle](https://attack.mitre.org/techniques/T1557/) for further information about this attack category. ### Patches A new setting, [`agent-tls-mode`](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-references/tls-settings), was added, which allows users to specify if agents will use `strict` certificate verification when connecting to Rancher. The field can be set to `strict` (which requires the agent to verify the certificate using only the Certificate Authority in the `cacerts` setting) or `system-store` (which allows the agent to verify the certificate using any Certificate Authority in the operating system's trust store). This setting will default to strict on new installs of Rancher `v2.8.6`, `v2.9.0`, and newer versions. When upgrading from a prior version, the current value will be kept. If updating from older versions, the settings must be manually configured. **Important:** For non-Windows nodes, this is fixed since `v2.8.6` and `v2.9.0`. For Windows nodes, this is fully fixed starting with `v2.8.8` and `v2.9.2` Patched versions include releases `v2.8.8` and `v2.9.2`. For non-Windows nodes, the fix was released with `v2.7.15`. However, if you are running Rancher `v2.7.x` and have Windows nodes, you must follow the below workaround to address this issue on those nodes. ### Workarounds If you can't update, please follow the standard security practices including: 1. Properly control the expiration and ownership of the domain used as the Rancher URL (the `server-url` of the Rancher cluster). 2. Enabling DNSSEC as a way to protect against DNS spoofing or hijacking attacks. 3. Properly clean up and decommission unused clusters and downstream clusters, instead of leaving them behind. For example, downstream clusters which are alive while the main Rancher server is no longer available. In some cases, Windows nodes added to RKE2 clusters may not be automatically updated with the desired `agent-tls-mode`. Windows clusters running at least the August patches (`v1.27.16`, `v1.28.13`, `v1.29.8`, `v1.30.4`) will be automatically updated. For Windows nodes running older versions of RKE2, this issue can be manually resolved by following these [instructions](https://github.com/rancherlabs/support-tools/tree/master/windows-agent-strict-verify). If you are running Rancher `v2.7.x` Windows nodes will not automatically update, and you must follow the above [instructions](https://github.com/rancherlabs/support-tools/tree/master/windows-agent-strict-verify), with the following notes: 1. This needs to be done for all existing Windows nodes and any new nodes provisioned. 2. You must omit the `DownloadWins` flag, and must instead manually download the `rancher-wins` version [0.4.18](https://github.com/rancher/wins/releases/tag/v0.4.18), or greater, from its GitHub repository and place it in the required directories: a. `c:\Windows` b. `c:\user\local\bin` 3. You must restart the nodes after running the script, simply restarting `rancher-wins` or RKE2 will result in [pod networking errors](https://github.com/rancher/rke2/issues/5551). The only scenario where you do not need to completely restart the node is if the cluster is running version `v1.27.16` or higher. ### Credits This issue was found and reported by Jarkko Vesiluoma from Redtest Security. ### For more information 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-3161

Published

Rancher agents can be hijacked by taking over the Rancher Server URL 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.7.0 before v2.7.15, from v2.8.0 before v2.8.8, from v2.9.0 before v2.9.2.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2024-22030

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.7.15",
                            "status": "affected",
                            "version": "2.7.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "2.8.8",
                            "status": "affected",
                            "version": "2.8.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "2.9.2",
                            "status": "affected",
                            "version": "2.9.0",
                            "versionType": "semver"
                        }
                    ]
                }

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

euvd · EUVD-2024-2807

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, 1:24:06 PM

dateUpdated: Oct 16, 2024, 2:25:43 PM

4 related source bulletins · separate from aliases

openSUSE-SU-2024:0350-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-0132 · CVE-2024-0133 · CVE-2024-10005 · CVE-2024-10006 · CVE-2024-10086 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-10452 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-39720 · CVE-2024-46872 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47401 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50052 · CVE-2024-50312 · CVE-2024-50354 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8185 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

WID-SEC-W-2024-0425: Rancher: Schwachstelle ermöglicht Privilegieneskalation

CVE-2024-22030

SUSE-SU-2024:3911-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

openSUSE-SU-2024:14447-1: govulncheck-vulndb-0.0.20241030T212825-1.1 on GA media

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

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-2024-22030

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-295

Original publisher date fields

published: 2024-10-16T14:15:04.753

lastModified: 2026-06-17T07:10:34.557

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-h4h5-9833-v2p4

Published

github.com/rancher/rancher

Go

SEMVER · introduced 2.7.0 → fixed 2.7.15

github.com/rancher/rancher

Go

SEMVER · introduced 2.8.0 → fixed 2.8.8

github.com/rancher/rancher

Go

SEMVER · introduced 2.9.0 → fixed 2.9.2

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

osv · GO-2024-3161

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 13:53 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current