github.com/argoproj/argo-cd/v2
Affected
- introduced
0, fixed2.1.15(semver)
Fixed versions
2.1.15
Fix
- Fixed version
2.1.15go get github.com/argoproj/argo-cd/[email protected]
Advisory
Also known as: CVE-2022-24904, GO-2022-0453
Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server
Impact
All unpatched versions of Argo CD starting with v0.7.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive files from Argo CD's repo-server.
A malicious Argo CD user with write access for a repository which is (or may be) used in a directory-type Application may commit a symlink which points to an out-of-bounds file.
Sensitive 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 JSON-formatted secrets which have been mounted as files on the repo-server.
Patches
A patch for this vulnerability has been released in the following Argo CD versions:
Workarounds
jsonnet.enable since the same build tool is used for both Jsonnet and plain-manifest ("directory") sources.Mitigations
Best practices which can mitigate risk
Credits
This vulnerability was originally discovered as part of the Trail of Bits audit, published March 12, 2021. The behavior was left unchanged at the time.
The vulnerability was independently re-discovered by @crenshaw-dev, who contributed the patch. A security audit by Ada Logics independently followed up on the Trail of Bits report around the same time.
References
For more information
Open an issue in the Argo CD issue tracker or discussions
Join us on Slack in channel #argo-cd
Medium Basis: The source's own band: MODERATE
0, fixed 2.1.15 (semver)2.1.15
2.1.15go get github.com/argoproj/argo-cd/[email protected]2.2.0, fixed 2.2.9 (semver)2.2.9
2.2.9go get github.com/argoproj/argo-cd/[email protected]2.3.0, fixed 2.3.4 (semver)2.3.4
2.3.4go get github.com/argoproj/argo-cd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0