CVE-2022-31036: Github.com/argoproj/argo cd Symlink Following Allows Leaking Out-of-bounds Vulnerability
MODERATECVE-2022-31036 is a MODERATE (CVSS 4.3) symlink following allows leaking out-of-bounds vulnerability (CWE-59: Improper Link Resolution Before File Access ('Link Following')) affecting Github.com/argoproj/argo cd libraries in the Go ecosystem. The issue involves symlink following allows leaking out-of-bounds yaml files from argo cd repo-server. Remediation is available by upgrading affected packages to version 2.1.16, 2.2.10, 2.3.5, 2.4.1.
CVE-2022-31036 at a Glance
Security Impact
CVSS: 4.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2022-31036
To remediate this vulnerability, upgrade all affected Github.com/argoproj/argo cd dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/argoproj/argo-cd to 2.1.16
Upgrade github.com/argoproj/argo-cd/v2 to 2.1.16
Upgrade github.com/argoproj/argo-cd/v2 to 2.2.10
Upgrade github.com/argoproj/argo-cd/v2 to 2.3.5
Upgrade github.com/argoproj/argo-cd/v2 to 2.4.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/argoproj/argo-cd
How to Check if You Are Affected
To determine whether your application is affected by CVE-2022-31036, inspect your project dependencies for Github.com/argoproj/argo cd:
inspect dependencies for github.com/argoproj/argo-cd
Analyze the terminal output to locate any version of Github.com/argoproj/argo cd in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.16), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following'), where the product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. In Github.com/argoproj/argo cd, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-31036 Affected Github.com/argoproj/argo cd Versions
5 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/argoproj/argo-cd
|
Go |
≥ 1.3.0
< 2.1.16
|
2.1.16
|
|
github.com/argoproj/argo-cd/v2
|
Go |
< 2.1.16
|
2.1.16
|
|
github.com/argoproj/argo-cd/v2
|
Go |
≥ 2.2.0
< 2.2.10
|
2.2.10
|
|
github.com/argoproj/argo-cd/v2
|
Go |
≥ 2.3.0
< 2.3.5
|
2.3.5
|
|
github.com/argoproj/argo-cd/v2
|
Go |
≥ 2.4.0
< 2.4.1
All 1 versions
2.4.0
|
2.4.1
|
References
Frequently Asked Questions
What is CVE-2022-31036?
Which Github.com/argoproj/argo cd versions are affected?
What version fixes CVE-2022-31036?
Is github.com/argoproj/argo-cd affected?
Is github.com/argoproj/argo-cd/v2 affected?
What is the CVSS score of CVE-2022-31036?
What CWE is associated with CVE-2022-31036?
How can I check Go dependencies for CVE-2022-31036?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-q4w5-4gq2-98vm",
"modified" : "2022-06-21T20:04:51Z",
"published" : "2022-06-21T20:04:51Z",
"aliases" : [ "CVE-2022-31036" ],
"summary" : "Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server",
"details" : "### Impact\n\nAll unpatched versions of Argo CD starting with v1.3.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive YAML files from Argo CD's repo-server.\n\nA malicious Argo CD user with write access for a repository which is (or may be) used in a Helm-type Application may commit a symlink which points to an out-of-bounds file. If the target file is a valid YAML file, the attacker can read the contents of that file.\n\nSensitive files which could be leaked include manifest files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any YAML-formatted secrets which have been mounted as files on the repo-server.\n\n### Patches\n\nA patch for this vulnerability has been released in the following Argo CD versions:\n\n* v2.4.1\n* v2.3.5\n* v2.2.10\n* v2.1.16\n\n### Workarounds\n\n* If you are using >=v2.3.0 and do not have any Helm-type Applications, [disable the Helm config management tool](https://argo-cd.readthedocs.io/en/stable/user-guide/tool_detection/#disable-built-in-tools).\n\n#### Mitigations\n\n* Avoid mounting YAML-formatted secrets as files on the repo-server.\n* Upgrade to >=2.3.0 to significantly reduce the risk of leaking out-of-bounds manifest files. Starting with 2.3.0, repository paths are randomized, and read permissions are restricted when manifests are not being actively being generated. This makes it very difficult to craft and use a malicious symlink.\n\n#### Best practices which can mitigate risk\n\n* Limit who has push access to manifest repositories.\n* Limit who is allowed to configure new source repositories.\n\n### Credits\n\nDisclosed by ADA Logics in a security audit of the Argo project sponsored by CNCF and facilitated by OSTIF. Thanks to Adam Korczynski and David Korczynski for their work on the audit.\n\n### References\n\n* List of [types of Applications](https://argo-cd.readthedocs.io/en/stable/user-guide/application_sources/), including Helm-type\n* [RBAC documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/), showing how to limit repository permissions\n\n### For more information\n\n* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/argoproj/argo-cd"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.3.0"
}, {
"fixed" : "2.1.16"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.8.7"
}
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/argoproj/argo-cd/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.1.16"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/argoproj/argo-cd/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.2.0"
}, {
"fixed" : "2.2.10"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/argoproj/argo-cd/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.3.0"
}, {
"fixed" : "2.3.5"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/argoproj/argo-cd/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.4.0"
}, {
"fixed" : "2.4.1"
} ]
} ],
"versions" : [ "2.4.0" ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/argoproj/argo-cd/security/advisories/GHSA-q4w5-4gq2-98vm"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-31036"
}, {
"type" : "WEB",
"url" : "https://github.com/argoproj/argo-cd/commit/04c305396458508a31d03d44afea07b1c620d7cd"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/argoproj/argo-cd"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-20", "CWE-59" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2022-06-21T20:04:51Z",
"nvd_published_at" : "2022-06-27T20:15:00Z"
}
}