CVE-2022-24905: Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.

Medium CVSS 4.3

CVE id
CVE-2022-24905
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Argo CD
Runtimes and servers
>= 0.6.1, < 2.1.15
>= 2.2.0, < 2.2.9
>= 2.3.0, < 2.3.4
2.1.15, 2.2.9, 2.3.4

How to fix it

Upgrade Argo CD to the fixed release of the line you run: 2.1.15, 2.2.9, 2.3.4.

  • 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. A vulnerability was found in Argo CD prior to versions 2.3.4, 2.2.9, and 2.1.15 that allows an attacker to spoof error messages on the login screen when single sign on (SSO) is enabled. In order to exploit this vulnerability, an attacker would have to trick the victim to visit a specially crafted URL which contains the message to be displayed. As far as the research of the Argo CD team concluded, it is not possible to specify any active content (e.g. Javascript) or other HTML fragments (e.g. clickable links) in the spoofed message. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. There are currently no known workarounds.

References

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.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

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.