CVE-2022-31016: GO-2022-0495 - DoS through large manifest files in Argo CD in github.com/argoproj/argo-cd

Quick answers

Is CVE-2022-31016 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-31016 being exploited in the wild.

How severe is CVE-2022-31016?

Low severity, with a CVSS score of 3.1, published 21 August 2024.

Which products and versions are affected?

github.com/argoproj/argo-cd (Go) SEMVER:introduced=0.7.0, SEMVER:introduced=0.7.0,fixed=2.1.16; github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=0,fixed=2.1.16, SEMVER:introduced=0,fixed=2.1.16,introduced=2.2.0,fixed=2.2.10,introduced=2.3.0,fixed=2.3.5,introduced=2.4.0,fixed=2.4.1.

Is there a fix for CVE-2022-31016?

Yes. github.com/argoproj/argo-cd (Go): upgrade to 2.1.16 or later; github.com/argoproj/argo-cd/v2 (Go): upgrade to 2.1.16, 2.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2022-31016?

Check whether you run github.com/argoproj/argo-cd (Go) or github.com/argoproj/argo-cd/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• github.com/argoproj/argo-cd (Go): upgrade to 2.1.16 or later

  go get github.com/argoproj/argo-cd@v2.1.16

• github.com/argoproj/argo-cd/v2 (Go): upgrade to 2.1.16, 2.4.1 or later

  go get github.com/argoproj/argo-cd/v2@v2.4.1

Affected products

• github.com/argoproj/argo-cd (Go) SEMVER:introduced=0.7.0, SEMVER:introduced=0.7.0,fixed=2.1.16
• github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=0,fixed=2.1.16, SEMVER:introduced=0,fixed=2.1.16,introduced=2.2.0,fixed=2.2.10,introduced=2.3.0,fixed=2.3.5,introduced=2.4.0,fixed=2.4.1

Identifiers

• CVE-2022-31016
• GHSA-jhqp-vf4w-rpwq
• GO-2022-0495