dbcve.org
Argo CdApplication · Argoproj

CVE-2022-31016

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-25
Fix available
A fix is available. Upgrade to 2.1.16 / 2.2.10 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-400

A single request can consume unbounded CPU, memory, or connections, so a modest amount of malicious traffic exhausts the service. The result is denial of service for everyone else. Remediation is enforcing limits, quotas, and timeouts on what any one request can use.

General guidance for the uncontrolled resource consumption class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Argo CdApplication
Affected:>= 0.7.0, < 2.1.16>= 2.2.0, < 2.2.10>= 2.3.0, < 2.3.5>= 2.4.0, < 2.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.16 / 2.2.10 / 2.3.5 or later
Fixed in 2.1.162.2.102.3.5
Vendor patch github.com →
Recommended fix High confidence

Upgrade to version 2.4.1 or later (or minimum 2.3.5, 2.2.10, or 2.1.16 depending on your current branch)

  1. Review the current Argo CD version running in your cluster using 'argocd version' or checking the deployment
  2. Backup your Argo CD configuration, application definitions, and any custom resources
  3. Plan the upgrade path: if on 0.7.0 to <2.1.16, upgrade to 2.1.16 or later; if on >=2.2.0 to <2.2.10, upgrade to 2.2.10 or later; if on >=2.3.0 to <2.3.5, upgrade to 2.3.5 or later; if on >=2.4.0 to <2.4.1, upgrade to 2.4.1 or later
  4. For Kubernetes installations using Helm: run 'helm repo update' then 'helm upgrade argocd argo/argo-cd --version <target-version>'
  5. For Kubernetes installations using kubectl: apply the new manifests from the target release at https://github.com/argoproj/argo-cd/releases/tag/v<target-version>
  6. Verify the upgrade by checking that all Argo CD pods are running: 'kubectl get pods -n argocd'
  7. Confirm the repo-server service is operational and can handle repository operations
  8. Test that applications can sync successfully to verify the fix is working

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31016 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data