Snyk - Open Source Security

Snyk test report

September 7th 2025, 12:22:10 am (UTC+00:00)

Scanned the following paths:
  • quay.io/argoproj/argocd:latest/argoproj/argocd/Dockerfile (deb)
  • quay.io/argoproj/argocd:latest/argoproj/argo-cd/v3//usr/local/bin/argocd (gomodules)
  • quay.io/argoproj/argocd:latest//usr/local/bin/kustomize (gomodules)
  • quay.io/argoproj/argocd:latest/helm/v3//usr/local/bin/helm (gomodules)
  • quay.io/argoproj/argocd:latest/git-lfs/git-lfs//usr/bin/git-lfs (gomodules)
17 known vulnerabilities
68 vulnerable dependency paths
2322 dependencies

Directory Traversal

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: tar
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and tar@1.35+dfsg-3.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest tar@1.35+dfsg-3.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest dpkg@1.22.18ubuntu2 tar@1.35+dfsg-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory.

Remediation

There is no fixed version for Ubuntu:25.04 tar.

References


Improper Authentication

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: pam/libpam0g
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and pam/libpam0g@1.5.3-7ubuntu4.3

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux@2.40.2-14ubuntu1.1 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux/login@1:4.16.0-2+really2.40.2-14ubuntu1.1 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam-modules@1.5.3-7ubuntu4.3 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam-modules@1.5.3-7ubuntu4.3 pam/libpam-modules-bin@1.5.3-7ubuntu4.3 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam-modules-bin@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam-modules@1.5.3-7ubuntu4.3 pam/libpam-modules-bin@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam-runtime@1.5.3-7ubuntu4.3 pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux@2.40.2-14ubuntu1.1 pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux/login@1:4.16.0-2+really2.40.2-14ubuntu1.1 pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam-runtime@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux@2.40.2-14ubuntu1.1 pam/libpam-runtime@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux/login@1:4.16.0-2+really2.40.2-14ubuntu1.1 pam/libpam-runtime@1.5.3-7ubuntu4.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

A flaw was found in pam_access, where certain rules in its configuration file are mistakenly treated as hostnames. This vulnerability allows attackers to trick the system by pretending to be a trusted hostname, gaining unauthorized access. This issue poses a risk for systems that rely on this feature to control who can access certain services or terminals.

Remediation

There is no fixed version for Ubuntu:25.04 pam.

References


Insecure Storage of Sensitive Information

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: pam/libpam0g
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and pam/libpam0g@1.5.3-7ubuntu4.3

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux@2.40.2-14ubuntu1.1 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux/login@1:4.16.0-2+really2.40.2-14ubuntu1.1 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam-modules@1.5.3-7ubuntu4.3 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam-modules@1.5.3-7ubuntu4.3 pam/libpam-modules-bin@1.5.3-7ubuntu4.3 pam/libpam0g@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam-modules-bin@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam-modules@1.5.3-7ubuntu4.3 pam/libpam-modules-bin@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam-runtime@1.5.3-7ubuntu4.3 pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux@2.40.2-14ubuntu1.1 pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux/login@1:4.16.0-2+really2.40.2-14ubuntu1.1 pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 pam/libpam-modules@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest pam/libpam-runtime@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux@2.40.2-14ubuntu1.1 pam/libpam-runtime@1.5.3-7ubuntu4.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux/login@1:4.16.0-2+really2.40.2-14ubuntu1.1 pam/libpam-runtime@1.5.3-7ubuntu4.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.

Remediation

There is no fixed version for Ubuntu:25.04 pam.

References


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/r3labs/diff/v3
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/r3labs/diff/v3@v3.0.2

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/r3labs/diff/v3@v3.0.2

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/hashicorp/go-version
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/hashicorp/go-version@v1.7.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/hashicorp/go-version@v1.7.0

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/hashicorp/go-retryablehttp
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/hashicorp/go-retryablehttp@v0.7.8

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/hashicorp/go-retryablehttp@v0.7.8

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/helm/v3 /usr/local/bin/helm
  • Package Manager: golang
  • Module: github.com/hashicorp/go-multierror
  • Introduced through: helm.sh/helm/v3@* and github.com/hashicorp/go-multierror@v1.1.1

Detailed paths

  • Introduced through: helm.sh/helm/v3@* github.com/hashicorp/go-multierror@v1.1.1

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/hashicorp/go-cleanhttp
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/hashicorp/go-cleanhttp@v0.5.2

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/hashicorp/go-cleanhttp@v0.5.2

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Module: github.com/gosimple/slug
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/gosimple/slug@v1.15.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/gosimple/slug@v1.15.0

MPL-2.0 license


Improper Encoding or Escaping of Output

medium severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: git/git-man
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest, git@1:2.48.1-0ubuntu1.1 and others

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest git@1:2.48.1-0ubuntu1.1 git/git-man@1:2.48.1-0ubuntu1.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest git@1:2.48.1-0ubuntu1.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest git-lfs@3.6.1-1 git@1:2.48.1-0ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.

Remediation

There is no fixed version for Ubuntu:25.04 git.

References


CVE-2024-56433

low severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: shadow/login.defs
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and shadow/login.defs@1:4.16.0-7ubuntu1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest shadow/login.defs@1:4.16.0-7ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest util-linux/login@1:4.16.0-2+really2.40.2-14ubuntu1.1 shadow/login.defs@1:4.16.0-7ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1 shadow/login.defs@1:4.16.0-7ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest shadow/passwd@1:4.16.0-7ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest openssh/openssh-client@1:9.9p1-3ubuntu3.1 shadow/passwd@1:4.16.0-7ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 adduser@3.137ubuntu2 shadow/passwd@1:4.16.0-7ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

Remediation

There is no fixed version for Ubuntu:25.04 shadow.

References


Double Free

low severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: patch
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and patch@2.7.6-7build3

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest patch@2.7.6-7build3

NVD Description

Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.

Remediation

There is no fixed version for Ubuntu:25.04 patch.

References


Release of Invalid Pointer or Reference

low severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: patch
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and patch@2.7.6-7build3

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest patch@2.7.6-7build3

NVD Description

Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

An Invalid Pointer vulnerability exists in GNU patch 2.7 via the another_hunk function, which causes a Denial of Service.

Remediation

There is no fixed version for Ubuntu:25.04 patch.

References


Information Exposure

low severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: libgcrypt20
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and libgcrypt20@1.11.0-6ubuntu1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest libgcrypt20@1.11.0-6ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/dirmngr@2.4.4-2ubuntu23.1 libgcrypt20@1.11.0-6ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/gpg@2.4.4-2ubuntu23.1 libgcrypt20@1.11.0-6ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/gpg-agent@2.4.4-2ubuntu23.1 libgcrypt20@1.11.0-6ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 gnupg2/gpgv@2.4.4-2ubuntu23.1 libgcrypt20@1.11.0-6ubuntu1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/gpg@2.4.4-2ubuntu23.1 gnupg2/gpgconf@2.4.4-2ubuntu23.1 libgcrypt20@1.11.0-6ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Remediation

There is no fixed version for Ubuntu:25.04 libgcrypt20.

References


Out-of-bounds Write

low severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: gnupg2/gpgv
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and gnupg2/gpgv@2.4.4-2ubuntu23.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/gpgv@2.4.4-2ubuntu23.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest apt@3.0.0 gnupg2/gpgv@2.4.4-2ubuntu23.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/dirmngr@2.4.4-2ubuntu23.1 gnupg2/gpgconf@2.4.4-2ubuntu23.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/gpg-agent@2.4.4-2ubuntu23.1 gnupg2/gpgconf@2.4.4-2ubuntu23.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/gpg@2.4.4-2ubuntu23.1 gnupg2/gpgconf@2.4.4-2ubuntu23.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/dirmngr@2.4.4-2ubuntu23.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/gpg@2.4.4-2ubuntu23.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest gnupg2/gpg-agent@2.4.4-2ubuntu23.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

Remediation

There is no fixed version for Ubuntu:25.04 gnupg2.

References


Allocation of Resources Without Limits or Throttling

low severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: glibc/libc-bin
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and glibc/libc-bin@2.41-6ubuntu1.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest glibc/libc-bin@2.41-6ubuntu1.1
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest glibc/libc6@2.41-6ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.

Remediation

There is no fixed version for Ubuntu:25.04 glibc.

References


Improper Input Validation

low severity

  • Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:25.04
  • Vulnerable module: coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@latest and coreutils@9.5-1ubuntu1.25.04.1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@latest coreutils@9.5-1ubuntu1.25.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:25.04 relevant fixed versions and status.

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

Remediation

There is no fixed version for Ubuntu:25.04 coreutils.

References