GHSA-XWF3-6RGV-939R
Vulnerability from github – Published: 2022-09-01 22:15 – Updated: 2022-09-01 22:15Flux CLI allows users to deploy Flux components into a Kubernetes cluster via command-line. The vulnerability allows other applications to replace the Flux deployment information with arbitrary content which is deployed into the target Kubernetes cluster instead.
The vulnerability is due to the improper handling of user-supplied input, which results in a path traversal that can be controlled by the attacker.
Impact
Users sharing the same shell between other applications and the Flux CLI commands could be affected by this vulnerability.
In some scenarios no errors may be presented, which may cause end users not to realise that something is amiss.
Workarounds
A safe workaround is to execute Flux CLI in ephemeral and isolated shell environments, which can ensure no persistent values exist from previous processes. However, upgrading to the latest version of the CLI is still the recommended mitigation strategy.
Credits
The Flux engineering team found and patched this vulnerability.
For more information
If you have any questions or comments about this advisory: - Open an issue in any of the affected repositories. - Contact us at the CNCF Flux Channel.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/fluxcd/flux2"
},
"ranges": [
{
"events": [
{
"introduced": "0.21.0"
},
{
"fixed": "0.32.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-36035"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2022-09-01T22:15:35Z",
"nvd_published_at": "2022-08-31T15:15:00Z",
"severity": "HIGH"
},
"details": "Flux CLI allows users to deploy Flux components into a Kubernetes cluster via command-line. The vulnerability allows other applications to replace the Flux deployment information with arbitrary content which is deployed into the target Kubernetes cluster instead.\n\nThe vulnerability is due to the improper handling of user-supplied input, which results in a path traversal that can be controlled by the attacker.\n\n### Impact\nUsers sharing the same shell between other applications and the Flux CLI commands could be affected by this vulnerability.\n\nIn some scenarios no errors may be presented, which may cause end users not to realise that something is amiss.\n\n### Workarounds\n\nA safe workaround is to execute Flux CLI in ephemeral and isolated shell environments, which can ensure no persistent values exist from previous processes. However, upgrading to the latest version of the CLI is still the recommended mitigation strategy.\n\n### Credits\nThe Flux engineering team found and patched this vulnerability.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in any of the affected repositories.\n- Contact us at the CNCF Flux Channel.\n",
"id": "GHSA-xwf3-6rgv-939r",
"modified": "2022-09-01T22:15:35Z",
"published": "2022-09-01T22:15:35Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/fluxcd/flux2/security/advisories/GHSA-xwf3-6rgv-939r"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-36035"
},
{
"type": "PACKAGE",
"url": "https://github.com/fluxcd/flux2"
},
{
"type": "WEB",
"url": "https://github.com/fluxcd/flux2/releases/tag/v0.32.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Flux CLI Workload Injection"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.