Skip to content
Fencer Intel
medium 4.3

CVE-2022-31036 json

Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server

published 4y ago modified 4mo ago also GHSA-q4w5-4gq2-98vm , GO-2022-0499 , EUVD-2022-6122

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All 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 for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. If you are using a version >=v2.3.0 and do not have any Helm-type Applications you may disable the Helm config management tool as a workaround.

Patch / fix

  • go github.com/argoproj/argo-cd 2.1.16
  • go github.com/argoproj/argo-cd/v2 2.1.16, 2.2.10, 2.3.5, 2.4.1
  • argoproj argo_cd 2.1.6

Is CVE-2022-31036 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-31036 updated cvss 4.3

argocd: vulnerable to a symlink following bug allowing a malicious user with repository write access

  • Red Hat OpenShift GitOps 1.3 openshift-gitops-1/argocd-rhel8 v1.3.11-4, openshift-gitops-1/argocd-rhel8 v1.3.12-1
    fixed: vendor fix RHSA-2022:5187
  • Red Hat OpenShift GitOps 1.4 openshift-gitops-1/argocd-rhel8 v1.4.9-3
    fixed: vendor fix RHSA-2022:5153
  • Red Hat OpenShift GitOps 1.5 openshift-gitops-1/argocd-rhel8 v1.5.3-2
    fixed: vendor fix RHSA-2022:5152
  • Red Hat OpenShift GitOps 1.3 openshift-gitops-1/dex-rhel8 v1.3.11-4, openshift-gitops-1/dex-rhel8 v1.3.12-1, openshift-gitops-1/gitops-rhel8 v1.3.11-4, openshift-gitops-1/gitops-rhel8 v1.3.12-1, openshift-gitops-1/kam-delivery-rhel8 v1.3.11-4, openshift-gitops-1/kam-delivery-rhel8 v1.3.12-1, +6 more Red Hat OpenShift GitOps 1.4 openshift-gitops-1/dex-rhel8 v1.4.9-3, openshift-gitops-1/gitops-rhel8 v1.4.9-3, openshift-gitops-1/kam-delivery-rhel8 v1.4.9-3, openshift-gitops-1/applicationset-rhel8 v1.4.9-3, openshift-gitops-1/gitops-rhel8-operator v1.4.9-3, openshift-gitops-1/gitops-operator-bundle v1.4.9-3 Red Hat OpenShift GitOps 1.5 openshift-gitops-1/dex-rhel8 v1.5.3-2, openshift-gitops-1/gitops-rhel8 v1.5.3-2, openshift-gitops-1/kam-delivery-rhel8 v1.5.3-2, openshift-gitops-1/applicationset-rhel8 v1.5.3-2, openshift-gitops-1/gitops-rhel8-operator v1.5.3-2, openshift-gitops-1/gitops-operator-bundle v1.5.3-2
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd
>=1.3.0, <2.1.16
>=1.3.0
2.1.16
go github.com/argoproj/argo-cd/v2
<2.1.16
>=2.2.0, <2.2.10
>=2.3.0, <2.3.5
>=2.4.0, <2.4.1
2.1.16
2.2.10
2.3.5
2.4.1

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-61 UNIX Symbolic Link (Symlink) Following
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.