4.3

CVSS Score

3.1

Basic Information

CVE ID

CVE-2022-31036

GHSA ID

GHSA-q4w5-4gq2-98vm

EPSS Score

0.4801%

CWE

CWE-20

Published

6/21/2022

Updated

1/27/2023

KEV Status

Technology

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2022-31036

CVE-2022-31036: Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server

Impact

All 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.

A 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.

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 YAML-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:

v2.4.1
v2.3.5
v2.2.10
v2.1.16

Workarounds

If you are using >=v2.3.0 and do not have any Helm-type Applications, disable the Helm config management tool.

Mitigations

Avoid mounting YAML-formatted secrets as files on the repo-server.
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.

Best practices which can mitigate risk

Limit who has push access to manifest repositories.
Limit who is allowed to configure new source repositories.

Credits

Disclosed 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.

References

List of types of Applications, including Helm-type
RBAC documentation, showing how to limit repository permissions

For more information

Open an issue in the Argo CD issue tracker or discussions
Join us on Slack in channel #argo-cd

(GitHub Advisory)

4.3

CVSS Score

3.1

Basic Information

CVE ID

CVE-2022-31036

GHSA ID

GHSA-q4w5-4gq2-98vm

EPSS Score

0.4801%

CWE

CWE-20

Published

6/21/2022

Updated

1/27/2023

KEV Status

Technology

Technical Details

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
github.com/argoproj/argo-cd	go	>= 1.3.0, <= 1.8.7	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

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability stems from improper symlink resolution in Helm file handling. Key indicators:

populateHelmAppDetails originally used filepath.Join() without validation (patched with pathutil.ResolveFilePath)
loadFileIntoIfExists accepted raw paths instead of validated ResolvedFilePath type
GetParameters loaded values.yaml without repository boundary checks All three functions lacked proper path validation against symlink attacks, allowing malicious users to read arbitrary YAML files through crafted symlinks in Helm applications.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

WAF Protection Rules

WAF Rule

### Imp**t *ll unp*t**** v*rsions o* *r*o ** st*rtin* wit* v*.*.* *r* vuln*r**l* to * symlink *ollowin* *u* *llowin* * m*li*ious us*r wit* r*pository writ* ****ss to l**k s*nsitiv* Y*ML *il*s *rom *r*o **'s r*po-s*rv*r. * m*li*ious *r*o ** us*r wit

Reasoning

T** vuln*r**ility st*ms *rom improp*r symlink r*solution in **lm *il* **n*lin*. K*y in*i**tors: *. popul*t***lm*pp**t*ils ori*in*lly us** *il*p*t*.Join() wit*out v*li**tion (p*t**** wit* p*t*util.R*solv**il*P*t*) *. lo***il*IntoI**xists ****pt** r*w

4.3

Basic Information

Concerned about an active attack path?

CVE-2022-31036: Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server

Impact

Patches

Workarounds

Mitigations

Best practices which can mitigate risk

Credits

References

For more information

4.3

Basic Information

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

WAF Protection Rules

WAF Rule

Reasoning

Vulnerability Intelligence
Miggo AI