CVE-2022-31105: Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.
Critical CVSS 9.6
- CVE id
- CVE-2022-31105
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Argo CD Runtimes and servers |
>= 2.3.0, < 2.3.6 >= 2.4.0, < 2.4.5 >= 0.4.0, < 2.2.11 |
2.2.11, 2.3.6, 2.4.5 |
How to fix it
Upgrade Argo CD to the fixed release of the line you run: 2.2.11, 2.3.6, 2.4.5.
- Upgrade Argo CD (the quay.io/argoproj/argocd image, or the argo-cd Helm chart) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with version 0.4.0 and prior to 2.2.11, 2.3.6, and 2.4.5 is vulnerable to an improper certificate validation bug which could cause Argo CD to trust a malicious (or otherwise untrustworthy) OpenID Connect (OIDC) provider. A patch for this vulnerability has been released in Argo CD versions 2.4.5, 2.3.6, and 2.2.11. There are no complete workarounds, but a partial workaround is available. Those who use an external OIDC provider (not the bundled Dex instance), can mitigate the issue by setting the oidc.config.rootCA field in the argocd-cm ConfigMap. This mitigation only forces certificate validation when the API server handles login flows. It does not force certificate verification when verifying tokens on API calls.
References
- CVE-2022-31105 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2022-31105
- Web: https://github.com/argoproj/argo-cd/releases/tag/v2.3.6
- Web: https://github.com/argoproj/argo-cd/releases/tag/v2.4.5
- Web: https://github.com/argoproj/argo-cd/security/advisories/GHSA-7943-82jg-wmw5
- Web: https://github.com/argoproj/argo-cd/releases/tag/v2.3.6
- Web: https://github.com/argoproj/argo-cd/releases/tag/v2.4.5
- Web: https://github.com/argoproj/argo-cd/security/advisories/GHSA-7943-82jg-wmw5
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.