CVE-2022-31016 json
Argo CD vulnerable to Uncontrolled Memory Consumption
published 2022-06-21 4 y ago modified 2026-06-17 4 mo ago also GHSA-jhqp-vf4w-rpwq , GO-2022-0495 , EUVD-2022-6080
- cvss
- 6.5
- 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 continuous deployment for Kubernetes. Argo CD versions v0.7.0 and later are vulnerable to an uncontrolled memory consumption bug, allowing an authorized malicious user to crash the repo-server service, resulting in a Denial of Service. The attacker must be an authenticated Argo CD user authorized to deploy Applications from a repository which contains (or can be made to contain) a large file. The fix for this vulnerability is available in versions 2.3.5, 2.2.10, 2.1.16, and later. There are no known workarounds. Users are recommended to upgrade.
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.16, 2.2.10, 2.3.5, 2.4.1
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-31016 updated cvss 6.5
argocd: vulnerable to an uncontrolled memory consumption bug
-
Red Hat OpenShift GitOps 1.3 openshift-gitops-1/argocd-rhel8 v1.3.11-4, openshift-gitops-1/argocd-rhel8 v1.3.12-1fixed: vendor fix RHSA-2022:5187
-
Red Hat OpenShift GitOps 1.4 openshift-gitops-1/argocd-rhel8 v1.4.9-3fixed: vendor fix RHSA-2022:5153
-
Red Hat OpenShift GitOps 1.5 openshift-gitops-1/argocd-rhel8 v1.5.3-2fixed: 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-2not 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
- 18 mo ago
Exploit prediction
0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/argoproj/argo-cd | >=0.7.0, <2.1.16 >=0.7.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
References
-
github.com
/argoproj/argo-cd/security/advisories/GHSA-jhqp-vf4w-rpwq
web, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-31016
advisory
-
github.com
/argoproj/argo-cd
package
Sources
- CVE List CVE-2022-31016
- GitHub Advisory GHSA-jhqp-vf4w-rpwq
- NVD CVE-2022-31016
- OSV GO-2022-0495
Fencer Vulns 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.