### Impact A vulnerability has been identified in Fleet when the webhook endpoint is configured without a secret; an attacker can forge webhook requests. The attacker doesn't need to know the specific repository or path configured in the GitRepo resource to make Fleet process these requests. An attacker can exploit this vulnerability to cause the following impacts: 1. Trigger continuous repository re-cloning, which increases network traffic and can deplete resources on the management cluster. 2. Downgrade running services to any historical revision available in the remote Git repository. This risk applies if the attacker has read access to the target Git repository and knows its configured path. Please consult the associated [MITRE ATT&CK - Technique - T1499.004: Endpoint Denial of Service](https://attack.mitre.org/techniques/T1499/) for further information about this category of attack. ### Patches To resolve this vulnerability, upgrade Fleet to a patched version. This upgrade version escapes the URL and path to the remote repository received from webhooks, which prevents regular expressions from being used as a replacement for the URL and path. Patched versions of Fleet include releases `v0.15.2`, `v0.14.6`, `0.13.11`, and `v0.12.15`. ### Workarounds If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret. ### Credits This security issue was reported by the following collaborators according to our responsible disclosure policy: - Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC). ### 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/).
### Impact A vulnerability has been identified in Fleet when the webhook endpoint is configured without a secret; an attacker can forge webhook requests. The attacker doesn't need to know the specific repository or path configured in the GitRepo resource to make Fleet process these requests. An attacker can exploit this vulnerability to cause the following impacts: 1. Trigger continuous repository re-cloning, which increases network traffic and can deplete resources on the management cluster. 2. Downgrade running services to any historical revision available in the remote Git repository. This risk applies if the attacker has read access to the target Git repository and knows its configured path. Please consult the associated [MITRE ATT&CK - Technique - T1499.004: Endpoint Denial of Service](https://attack.mitre.org/techniques/T1499/) for further information about this category of attack. ### Patches To resolve this vulnerability, upgrade Fleet to a patched version. This upgrade version escapes the URL and path to the remote repository received from webhooks, which prevents regular expressions from being used as a replacement for the URL and path. Patched versions of Fleet include releases `v0.15.2`, `v0.14.6`, `0.13.11`, and `v0.12.15`. ### Workarounds If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret. ### Credits This security issue was reported by the following collaborators according to our responsible disclosure policy: - Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC). ### 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/).
Update github.com/rancher/fleet to 0.15.2; github.com/rancher/fleet to 0.14.6; github.com/rancher/fleet to 0.13.11; github.com/rancher/fleet to 0.12.15 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanRancher Fleet has Unauthenticated Webhook: Regex Injection via Unsanitized Repository URL Components affects github.com/rancher/fleet (go), github.com/rancher/fleet (go), github.com/rancher/fleet (go), github.com/rancher/fleet (go). Severity is high. ### Impact A vulnerability has been identified in Fleet when the webhook endpoint is configured without a secret; an attacker can forge webhook requests. The attacker doesn't need to know the specific repository or path configured in the GitRepo resource to make Fleet process these requests. An attacker can exploit this vulnerability to cause the following impacts: 1. Trigger continuous repository re-cloning, which increases network traffic and can deplete resources on the management cluster. 2. Downgrade running services to any historical revision available in the remote Git repository. This risk applies if the attacker has read access to the target Git repository and knows its configured path. Please consult the associated [MITRE ATT&CK - Technique - T1499.004: Endpoint Denial of Service](https://attack.mitre.org/techniques/T1499/) for further information about this category of attack. ### Patches To resolve this vulnerability, upgrade Fleet to a patched version. This upgrade version escapes the URL and path to the remote repository received from webhooks, which prevents regular expressions from being used as a replacement for the URL and path. Patched versions of Fleet include releases `v0.15.2`, `v0.14.6`, `0.13.11`, and `v0.12.15`. ### Workarounds If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret. ### Credits This security issue was reported by the following collaborators according to our responsible disclosure policy: - Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC). ### 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/).
AI coding agents often install or upgrade packages automatically in go. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/rancher/fleetgo | >=0.15.0,<0.15.2 | 0.15.2 |
| github.com/rancher/fleetgo | >=0.14.0,<0.14.6 | 0.14.6 |
| github.com/rancher/fleetgo | >=0.13.0,<0.13.11 | 0.13.11 |
| github.com/rancher/fleetgo | >=0.12.0,<0.12.15 | 0.12.15 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate github.com/rancher/fleet to 0.15.2; github.com/rancher/fleet to 0.14.6; github.com/rancher/fleet to 0.13.11; github.com/rancher/fleet to 0.12.15 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanRancher Fleet has Unauthenticated Webhook: Regex Injection via Unsanitized Repository URL Components affects github.com/rancher/fleet (go), github.com/rancher/fleet (go), github.com/rancher/fleet (go), github.com/rancher/fleet (go). Severity is high. ### Impact A vulnerability has been identified in Fleet when the webhook endpoint is configured without a secret; an attacker can forge webhook requests. The attacker doesn't need to know the specific repository or path configured in the GitRepo resource to make Fleet process these requests. An attacker can exploit this vulnerability to cause the following impacts: 1. Trigger continuous repository re-cloning, which increases network traffic and can deplete resources on the management cluster. 2. Downgrade running services to any historical revision available in the remote Git repository. This risk applies if the attacker has read access to the target Git repository and knows its configured path. Please consult the associated [MITRE ATT&CK - Technique - T1499.004: Endpoint Denial of Service](https://attack.mitre.org/techniques/T1499/) for further information about this category of attack. ### Patches To resolve this vulnerability, upgrade Fleet to a patched version. This upgrade version escapes the URL and path to the remote repository received from webhooks, which prevents regular expressions from being used as a replacement for the URL and path. Patched versions of Fleet include releases `v0.15.2`, `v0.14.6`, `0.13.11`, and `v0.12.15`. ### Workarounds If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret. ### Credits This security issue was reported by the following collaborators according to our responsible disclosure policy: - Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC). ### 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/).
AI coding agents often install or upgrade packages automatically in go. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/rancher/fleetgo | >=0.15.0,<0.15.2 | 0.15.2 |
| github.com/rancher/fleetgo | >=0.14.0,<0.14.6 | 0.14.6 |
| github.com/rancher/fleetgo | >=0.13.0,<0.13.11 | 0.13.11 |
| github.com/rancher/fleetgo | >=0.12.0,<0.12.15 | 0.12.15 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard