Snyk - Open Source Security

Snyk test report

March 29th 2026, 12:45:33 am (UTC+00:00)

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

Incorrect Authorization

critical severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: google.golang.org/grpc
  • Introduced through: github.com/argoproj/argo-cd/v3@* and google.golang.org/grpc@v1.73.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* google.golang.org/grpc@v1.73.0

Overview

Affected versions of this package are vulnerable to Incorrect Authorization in the processing of HTTP/2 :path pseudo-headers in handleStream(). An attacker can gain unauthorized access to restricted resources by sending requests with malformed :path headers that omit the leading slash. This is only exploitable if the server uses path-based authorization interceptors, has deny rules that use canonical paths with leading slashes, and has a fallback allow rule in its policy.

Workaround

This vulnerability can be mitigated by adding a validating interceptor that rejects requests with malformed paths, configuring infrastructure (such as reverse proxies) to enforce strict HTTP/2 compliance, or switching to a default-deny authorization policy.

Remediation

Upgrade google.golang.org/grpc to version 1.79.3 or higher.

References


Untrusted Search Path

high severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: go.opentelemetry.io/otel/sdk/resource
  • Introduced through: github.com/argoproj/argo-cd/v3@* and go.opentelemetry.io/otel/sdk/resource@v1.36.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* go.opentelemetry.io/otel/sdk/resource@v1.36.0

Overview

Affected versions of this package are vulnerable to Untrusted Search Path in resource detection code which executes ioreg, when the PATH environment variable is modified to include a malicious executable. An attacker can execute arbitrary code within the context of the application by placing a malicious binary earlier in the search path.

Note: This vulnerability is only exploitable on MacOS/Darwin systems.

Remediation

Upgrade go.opentelemetry.io/otel/sdk/resource to version 1.40.0 or higher.

References


Directory Traversal

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: tar
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and tar@1.35+dfsg-3build1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 tar@1.35+dfsg-3build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 dash@0.5.12-6ubuntu5 dpkg@1.22.6ubuntu6.5 tar@1.35+dfsg-3build1

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:24.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:24.04 tar.

References


Directory Traversal

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: pam/libpam0g
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and pam/libpam0g@1.5.3-5ubuntu5.5

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 pam/libpam0g@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 shadow/login@1:4.13+dfsg1-4ubuntu3.2 pam/libpam0g@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 util-linux@2.39.3-9ubuntu6.5 pam/libpam0g@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 adduser@3.137ubuntu1 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2 pam/libpam0g@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 adduser@3.137ubuntu1 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2 pam/libpam-modules@1.5.3-5ubuntu5.5 pam/libpam0g@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 adduser@3.137ubuntu1 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2 pam/libpam-modules@1.5.3-5ubuntu5.5 pam/libpam-modules-bin@1.5.3-5ubuntu5.5 pam/libpam0g@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 pam/libpam-modules-bin@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 adduser@3.137ubuntu1 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2 pam/libpam-modules@1.5.3-5ubuntu5.5 pam/libpam-modules-bin@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 pam/libpam-modules@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 pam/libpam-runtime@1.5.3-5ubuntu5.5 pam/libpam-modules@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 shadow/login@1:4.13+dfsg1-4ubuntu3.2 pam/libpam-modules@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 adduser@3.137ubuntu1 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2 pam/libpam-modules@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 pam/libpam-runtime@1.5.3-5ubuntu5.5
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 shadow/login@1:4.13+dfsg1-4ubuntu3.2 pam/libpam-runtime@1.5.3-5ubuntu5.5

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:24.04 relevant fixed versions and status.

A flaw was found in linux-pam. The pam_namespace module may improperly handle user-controlled paths, allowing local users to exploit symlink attacks and race conditions to elevate their privileges to root. This CVE provides a "complete" fix for CVE-2025-6020.

Remediation

There is no fixed version for Ubuntu:24.04 pam.

References


Inefficient Algorithmic Complexity

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/helm/v3 /usr/local/bin/helm
  • Package Manager: golang
  • Vulnerable module: golang.org/x/net/html
  • Introduced through: helm.sh/helm/v3@* and golang.org/x/net/html@v0.40.0

Detailed paths

  • Introduced through: helm.sh/helm/v3@* golang.org/x/net/html@v0.40.0

Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity via the html.Parse function due to quadratic parsing complexity when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.

Remediation

Upgrade golang.org/x/net/html to version 0.45.0 or higher.

References


Infinite loop

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/helm/v3 /usr/local/bin/helm
  • Package Manager: golang
  • Vulnerable module: golang.org/x/net/html
  • Introduced through: helm.sh/helm/v3@* and golang.org/x/net/html@v0.40.0

Detailed paths

  • Introduced through: helm.sh/helm/v3@* golang.org/x/net/html@v0.40.0

Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Infinite loop via the html.Parse function. An attacker can cause resource exhaustion and disrupt service availability by submitting specially crafted HTML input that triggers an infinite parsing loop.

Remediation

Upgrade golang.org/x/net/html to version 0.45.0 or higher.

References


Improper Verification of Cryptographic Signature

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: gnupg2/gpgv
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and gnupg2/gpgv@2.4.4-2ubuntu17.4

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpgv@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 gnupg2/gpgv@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/dirmngr@2.4.4-2ubuntu17.4 gnupg2/gpgconf@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg-agent@2.4.4-2ubuntu17.4 gnupg2/gpgconf@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg@2.4.4-2ubuntu17.4 gnupg2/gpgconf@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/dirmngr@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg-agent@2.4.4-2ubuntu17.4

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:24.04 relevant fixed versions and status.

In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.

Remediation

There is no fixed version for Ubuntu:24.04 gnupg2.

References


Improper Validation of Specified Type of Input

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: github.com/vmihailenco/msgpack/v5
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/vmihailenco/msgpack/v5@v5.4.1

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/vmihailenco/msgpack/v5@v5.4.1

Overview

Affected versions of this package are vulnerable to Improper Validation of Specified Type of Input in the calls plugin when handling websocket messages containing malformed msgpack frames. An attacker can cause the server to consume excessive memory and crash by sending specially crafted websocket requests.

Remediation

There is no fixed version for github.com/vmihailenco/msgpack/v5.

References


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/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.1

Detailed paths

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

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/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:v3.1.13/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.7

Detailed paths

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

MPL-2.0 license


MPL-2.0 license

medium severity

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/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:v3.1.13/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:v3.1.13/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 Validation of Integrity Check Value

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argo-cd/v3 /usr/local/bin/argocd
  • Package Manager: golang
  • Vulnerable module: github.com/go-git/go-git/v5/storage/filesystem
  • Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/go-git/go-git/v5/storage/filesystem@v5.14.0

Detailed paths

  • Introduced through: github.com/argoproj/argo-cd/v3@* github.com/go-git/go-git/v5/storage/filesystem@v5.14.0

Overview

Affected versions of this package are vulnerable to Improper Validation of Integrity Check Value for .idx and .pack files. An attacker can cause the application to consume corrupted files, leading to unexpected errors, due to checksums not being checked in the loadIdxFile() function.

Workaround

This vulnerability can be mitigated by running 'git fsck' from the git CLI to check for data corruption on a given repository.

Remediation

Upgrade github.com/go-git/go-git/v5/storage/filesystem to version 5.16.5 or higher.

References


Improper Encoding or Escaping of Output

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: git/git-man
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13, git@1:2.43.0-1ubuntu7.3 and others

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 git@1:2.43.0-1ubuntu7.3 git/git-man@1:2.43.0-1ubuntu7.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 git@1:2.43.0-1ubuntu7.3
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 git-lfs@3.4.1-1ubuntu0.3 git@1:2.43.0-1ubuntu7.3

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:24.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:24.04 git.

References


Link Following

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: git-lfs
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and git-lfs@3.4.1-1ubuntu0.3

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 git-lfs@3.4.1-1ubuntu0.3

NVD Description

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

Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull commands do not check for symbolic links before writing to files in the working tree, allowing an attacker to craft a repository containing symbolic or hard links that cause Git LFS to write to arbitrary file system locations accessible to the user running these commands. As well, when the git lfs checkout and git lfs pull commands are run in a bare repository, they could write to files visible outside the repository. The vulnerability is fixed in version 3.7.1. As a workaround, support for symlinks in Git may be disabled by setting the core.symlinks configuration option to false, after which further clones and fetches will not create symbolic links. However, any symbolic or hard links in existing repositories will still provide the opportunity for Git LFS to write to their targets.

Remediation

Upgrade Ubuntu:24.04 git-lfs to version 3.4.1-1ubuntu0.3+esm2 or higher.

References


Arbitrary Code Injection

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: git-lfs
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and git-lfs@3.4.1-1ubuntu0.3

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 git-lfs@3.4.1-1ubuntu0.3

NVD Description

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

Git LFS is a Git extension for versioning large files. When Git LFS requests credentials from Git for a remote host, it passes portions of the host's URL to the git-credential(1) command without checking for embedded line-ending control characters, and then sends any credentials it receives back from the Git credential helper to the remote host. By inserting URL-encoded control characters such as line feed (LF) or carriage return (CR) characters into the URL, an attacker may be able to retrieve a user's Git credentials. This problem exists in all previous versions and is patched in v3.6.1. All users should upgrade to v3.6.1. There are no workarounds known at this time.

Remediation

Upgrade Ubuntu:24.04 git-lfs to version 3.4.1-1ubuntu0.3+esm2 or higher.

References


Algorithmic Complexity

medium severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: expat/libexpat1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13, git@1:2.43.0-1ubuntu7.3 and others

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 git@1:2.43.0-1ubuntu7.3 expat/libexpat1@2.6.1-2ubuntu0.4

NVD Description

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

In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.

Remediation

There is no fixed version for Ubuntu:24.04 expat.

References


CVE-2024-56433

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: shadow/passwd
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and shadow/passwd@1:4.13+dfsg1-4ubuntu3.2

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 openssh/openssh-client@1:9.6p1-3ubuntu13.15 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 adduser@3.137ubuntu1 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 shadow/login@1:4.13+dfsg1-4ubuntu3.2

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:24.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:24.04 shadow.

References


Release of Invalid Pointer or Reference

low severity
Exploit: Not Defined

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

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 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:24.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:24.04 patch.

References


Double Free

low severity
Exploit: Not Defined

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

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 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:24.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:24.04 patch.

References


Covert Timing Channel

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: libgcrypt20
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and libgcrypt20@1.10.3-2build1

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 libgcrypt20@1.10.3-2build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/dirmngr@2.4.4-2ubuntu17.4 libgcrypt20@1.10.3-2build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg@2.4.4-2ubuntu17.4 libgcrypt20@1.10.3-2build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg-agent@2.4.4-2ubuntu17.4 libgcrypt20@1.10.3-2build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 apt/libapt-pkg6.0t64@2.8.3 libgcrypt20@1.10.3-2build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 gnupg2/gpgv@2.4.4-2ubuntu17.4 libgcrypt20@1.10.3-2build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg@2.4.4-2ubuntu17.4 gnupg2/gpgconf@2.4.4-2ubuntu17.4 libgcrypt20@1.10.3-2build1
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 adduser@3.137ubuntu1 shadow/passwd@1:4.13+dfsg1-4ubuntu3.2 pam/libpam-modules@1.5.3-5ubuntu5.5 systemd/libsystemd0@255.4-1ubuntu8.14 libgcrypt20@1.10.3-2build1

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:24.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:24.04 libgcrypt20.

References


Out-of-bounds Write

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: gnupg2/gpgv
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and gnupg2/gpgv@2.4.4-2ubuntu17.4

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpgv@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 apt@2.8.3 gnupg2/gpgv@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/dirmngr@2.4.4-2ubuntu17.4 gnupg2/gpgconf@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg-agent@2.4.4-2ubuntu17.4 gnupg2/gpgconf@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg@2.4.4-2ubuntu17.4 gnupg2/gpgconf@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/dirmngr@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg@2.4.4-2ubuntu17.4
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 gnupg2/gpg-agent@2.4.4-2ubuntu17.4

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:24.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:24.04 gnupg2.

References


Allocation of Resources Without Limits or Throttling

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: glibc/libc-bin
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and glibc/libc-bin@2.39-0ubuntu8.7

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 glibc/libc-bin@2.39-0ubuntu8.7
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 glibc/libc6@2.39-0ubuntu8.7

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:24.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:24.04 glibc.

References


Improper Input Validation

low severity
Exploit: Not Defined

  • Manifest file: quay.io/argoproj/argocd:v3.1.13/argoproj/argocd Dockerfile
  • Package Manager: ubuntu:24.04
  • Vulnerable module: coreutils
  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 and coreutils@9.4-3ubuntu6.2

Detailed paths

  • Introduced through: docker-image|quay.io/argoproj/argocd@v3.1.13 coreutils@9.4-3ubuntu6.2

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:24.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:24.04 coreutils.

References