# Snyk test report

December 14th 2025, 12:33:02 am (UTC+00:00)

Scanned the following paths:

- quay.io/argoproj/argocd:v3.0.20/argoproj/argocd/Dockerfile (deb)
- quay.io/argoproj/argocd:v3.0.20/argoproj/argo-cd/v3//usr/local/bin/argocd (gomodules)
- quay.io/argoproj/argocd:v3.0.20//usr/local/bin/kustomize (gomodules)
- quay.io/argoproj/argocd:v3.0.20/helm/v3//usr/local/bin/helm (gomodules)
- quay.io/argoproj/argocd:v3.0.20/git-lfs/git-lfs//usr/bin/git-lfs (gomodules)

29 known vulnerabilities
73 vulnerable dependency paths
2358 dependencies

## Improper Handling of Unexpected Data Type

high severity

- Manifest file: quay.io/argoproj/argocd:v3.0.20/argoproj/argo-cd/v3 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh/agent
- Introduced through: github.com/argoproj/argo-cd/v3@* and golang.org/x/crypto/ssh/agent@v0.38.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@* › golang.org/x/crypto/ssh/agent@v0.38.0

## Overview

Affected versions of this package are vulnerable to Improper Handling of Unexpected Data Type when functions including `List()` and `SignWithFlags()` process `*successAgentMsg`. This can be triggered by a malicious agent sending a single `0x06` byte (`SSH_AGENT_SUCCESS`), which is unmarshalled into a `*successAgentMsg`, causing a panic and client crash.

## Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

- High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

- Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm `ws` package

## Remediation

Upgrade `golang.org/x/crypto/ssh/agent` to version 0.43.0 or higher.

## References

- GitHub Commit
- GitHub Issue

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

high severity

- Manifest file: quay.io/argoproj/argocd:v3.0.20/argoproj/argo-cd/v3 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: github.com/expr-lang/expr/vm
- Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/expr-lang/expr/vm@v1.16.9

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@* › github.com/expr-lang/expr/vm@v1.16.9

## Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the `parseExpression()` function in `parser.go`, due to the unrestricted size of input strings, which can cause the generation of large Abstract Syntax Trees (ASTs). An attacker can crash the application by supplying excessively long deeply nested expression strings.

## Workaround

This vulnerability can be avoided by checking and limiting the length of input expressions before parsing them.

## Remediation

Upgrade `github.com/expr-lang/expr/vm` to version 1.17.0 or higher.

## References

- GitHub Commit
- GitHub PR

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

high severity

- Manifest file: quay.io/argoproj/argocd:v3.0.20/argoproj/argo-cd/v3 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: github.com/expr-lang/expr/parser
- Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/expr-lang/expr/parser@v1.16.9

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@* › github.com/expr-lang/expr/parser@v1.16.9

## Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the `parseExpression()` function in `parser.go`, due to the unrestricted size of input strings, which can cause the generation of large Abstract Syntax Trees (ASTs). An attacker can crash the application by supplying excessively long deeply nested expression strings.

## Workaround

This vulnerability can be avoided by checking and limiting the length of input expressions before parsing them.

## Remediation

Upgrade `github.com/expr-lang/expr/parser` to version 1.17.0 or higher.

## References

- GitHub Commit
- GitHub PR

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

high severity

- Manifest file: quay.io/argoproj/argocd:v3.0.20/argoproj/argo-cd/v3 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: github.com/expr-lang/expr/conf
- Introduced through: github.com/argoproj/argo-cd/v3@* and github.com/expr-lang/expr/conf@v1.16.9

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@* › github.com/expr-lang/expr/conf@v1.16.9

## Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the `parseExpression()` function in `parser.go`, due to the unrestricted size of input strings, which can cause the generation of large Abstract Syntax Trees (ASTs). An attacker can crash the application by supplying excessively long deeply nested expression strings.

## Workaround

This vulnerability can be avoided by checking and limiting the length of input expressions before parsing them.

## Remediation

Upgrade `github.com/expr-lang/expr/conf` to version 1.17.0 or higher.

## References

- GitHub Commit
- GitHub PR

More about this vulnerability

## Directory Traversal

medium severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › tar@1.35+dfsg-3build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-45582
- https://github.com/i900008/vulndb/blob/main/Gnu_tar_vuln.md
- https://www.gnu.org/software/tar/
- https://lists.gnu.org/archive/html/bug-tar/2025-08/msg00012.html
- https://www.gnu.org/software/tar/manual/html_node/Integrity.html
- https://www.gnu.org/software/tar/manual/html_node/Security-rules-of-thumb.html
- http://www.openwall.com/lists/oss-security/2025/11/01/6

More about this vulnerability

## Directory Traversal

medium severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › pam/libpam0g@1.5.3-5ubuntu5.5
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › shadow/login@1:4.13+dfsg1-4ubuntu3.2 › pam/libpam0g@1.5.3-5ubuntu5.5
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › util-linux@2.39.3-9ubuntu6.3 › pam/libpam0g@1.5.3-5ubuntu5.5
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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.0.20 › 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.0.20 › 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.0.20 › pam/libpam-modules-bin@1.5.3-5ubuntu5.5
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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.0.20 › pam/libpam-modules@1.5.3-5ubuntu5.5
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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.0.20 › 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.0.20 › 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.0.20 › pam/libpam-runtime@1.5.3-5ubuntu5.5
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-8941
- https://access.redhat.com/security/cve/CVE-2025-8941
- https://bugzilla.redhat.com/show_bug.cgi?id=2388220
- https://access.redhat.com/errata/RHSA-2025:14557
- https://access.redhat.com/errata/RHSA-2025:15100
- https://access.redhat.com/errata/RHSA-2025:15104
- https://access.redhat.com/errata/RHSA-2025:15107
- https://access.redhat.com/errata/RHSA-2025:15099
- https://access.redhat.com/errata/RHSA-2025:15101
- https://access.redhat.com/errata/RHSA-2025:15102
- https://access.redhat.com/errata/RHSA-2025:15103
- https://access.redhat.com/errata/RHSA-2025:15105
- https://access.redhat.com/errata/RHSA-2025:15106
- https://access.redhat.com/errata/RHSA-2025:15709
- https://access.redhat.com/errata/RHSA-2025:15828
- https://access.redhat.com/errata/RHSA-2025:15827
- https://access.redhat.com/errata/RHSA-2025:16524
- https://access.redhat.com/errata/RHSA-2025:18219
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:21885

More about this vulnerability

## Improper Validation of Syntactic Correctness of Input

medium severity

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

### Detailed paths

- Introduced through: helm.sh/helm/v3@* › golang.org/x/net/html@v0.33.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 Improper Validation of Syntactic Correctness of Input in the tokenizer in `token.go`, which incorrectly interprets tags as closing tags, allowing malicious input to be incorrectly processed and the DOM to be corrupted.

## Details

Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, `<` can be coded as `&lt`; and `>` can be coded as `&gt`; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses `<` and `>` as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

### Types of attacks

There are a few methods by which XSS can be manipulated:

Type | Origin | Description
--- | --- | ---
Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated |  | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

### Affected environments

The following environments are susceptible to an XSS attack:

- Web servers
- Application servers
- Web application environments

### How to prevent

This section describes the top best practices designed to specifically protect your code:

- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as `?`, `&`, `/`, `<`, `>` and spaces to their respective HTML or URL encoded equivalents.
- Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

## Remediation

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

## References

- GitHub Commit
- GitHub Issue
- Google Groups Announcement

More about this vulnerability

## Out-of-bounds Read

medium severity

- Manifest file: quay.io/argoproj/argocd:v3.0.20/argoproj/argo-cd/v3 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh/agent
- Introduced through: github.com/argoproj/argo-cd/v3@* and golang.org/x/crypto/ssh/agent@v0.38.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@* › golang.org/x/crypto/ssh/agent@v0.38.0

## Overview

Affected versions of this package are vulnerable to Out-of-bounds Read via the SSH Agent servers. An attacker can cause a panic and disrupt service availability by sending a specially crafted, malformed message that triggers an out-of-bounds read.

## Remediation

Upgrade `golang.org/x/crypto/ssh/agent` to version 0.45.0 or higher.

## References

- GO-2025-4135
- go.dev Commit
- go.dev Issue
- Google Groups Forum

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

medium severity

- Manifest file: quay.io/argoproj/argocd:v3.0.20/argoproj/argo-cd/v3 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/argoproj/argo-cd/v3@* and golang.org/x/crypto/ssh@v0.38.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@* › golang.org/x/crypto/ssh@v0.38.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the SSH servers. An attacker can exhaust system memory resources by sending GSSAPI authentication requests with an excessive number of mechanisms specified.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.45.0 or higher.

## References

- Fix Commit
- GO-2025-4134
- go.dev Issue
- Google Groups Forum

More about this vulnerability

## MPL-2.0 license

medium severity

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

More about this vulnerability

## MPL-2.0 license

medium severity

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

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

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

More about this vulnerability

## MPL-2.0 license

medium severity

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

More about this vulnerability

## MPL-2.0 license

medium severity

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

More about this vulnerability

## MPL-2.0 license

medium severity

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

More about this vulnerability

## Improper Encoding or Escaping of Output

medium severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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.0.20 › git@1:2.43.0-1ubuntu7.3
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-52005
- https://github.com/git/git/security/advisories/GHSA-7jjc-gg6m-3329
- https://lore.kernel.org/git/1M9FnZ-1taoNo1wwh-00ESSd@mail.gmx.net

More about this vulnerability

## Algorithmic Complexity

medium severity

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

### Detailed paths

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

## 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-66382
- https://github.com/libexpat/libexpat/issues/1076
- http://www.openwall.com/lists/oss-security/2025/12/02/1

More about this vulnerability

## CVE-2024-56433

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › shadow/passwd@1:4.13+dfsg1-4ubuntu3.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › openssh/openssh-client@1:9.6p1-3ubuntu13.14 › shadow/passwd@1:4.13+dfsg1-4ubuntu3.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › apt@2.8.3 › adduser@3.137ubuntu1 › shadow/passwd@1:4.13+dfsg1-4ubuntu3.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-56433
- https://github.com/shadow-maint/shadow/blob/e2512d5741d4a44bdd81a8c2d0029b6222728cf0/etc/login.defs#L238-L241
- https://github.com/shadow-maint/shadow/issues/1157
- https://github.com/shadow-maint/shadow/releases/tag/4.4

More about this vulnerability

## Release of Invalid Pointer or Reference

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2021-45261
- https://savannah.gnu.org/bugs/?61685

More about this vulnerability

## Double Free

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-6952
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6952
- https://security-tracker.debian.org/tracker/CVE-2018-6952
- https://security.gentoo.org/glsa/201904-17
- https://savannah.gnu.org/bugs/index.php?53133
- https://access.redhat.com/errata/RHSA-2019:2033
- http://www.securityfocus.com/bid/103047

More about this vulnerability

## CVE-2024-41996

low severity

- Manifest file: quay.io/argoproj/argocd:v3.0.20/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:24.04
- Vulnerable module: openssl/libssl3t64
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 and openssl/libssl3t64@3.0.13-0ubuntu3.6

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › coreutils@9.4-3ubuntu6.1 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › cyrus-sasl2/libsasl2-modules@2.1.28+dfsg1-5ubuntu3.1 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › libfido2/libfido2-1@1.14.0-1build3 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › openssh/openssh-client@1:9.6p1-3ubuntu13.14 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › ca-certificates@20240203 › openssl@3.0.13-0ubuntu3.6 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › git@1:2.43.0-1ubuntu7.3 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.6 › libssh/libssh-4@0.10.6-2ubuntu0.1 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › git@1:2.43.0-1ubuntu7.3 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.6 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2.6 › krb5/libkrb5-3@1.20.1-6ubuntu2.6 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › git@1:2.43.0-1ubuntu7.3 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.6 › openldap/libldap2@2.6.7+dfsg-1~exp1ubuntu8.2 › cyrus-sasl2/libsasl2-2@2.1.28+dfsg1-5ubuntu3.1 › openssl/libssl3t64@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › openssl@3.0.13-0ubuntu3.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › ca-certificates@20240203 › openssl@3.0.13-0ubuntu3.6

## NVD Description

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

Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.

## Remediation

There is no fixed version for `Ubuntu:24.04` `openssl`.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-41996
- https://dheatattack.gitlab.io/details/
- https://dheatattack.gitlab.io/faq/
- https://gist.github.com/c0r0n3r/abccc14d4d96c0442f3a77fa5ca255d1

More about this vulnerability

## NULL Pointer Dereference

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › git@1:2.43.0-1ubuntu7.3 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.6 › libssh/libssh-4@0.10.6-2ubuntu0.1

## NVD Description

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

A flaw was found in libssh, a library that implements the SSH protocol. When calculating the session ID during the key exchange (KEX) process, an allocation failure in cryptographic functions may lead to a NULL pointer dereference. This issue can cause the client or server to crash.

## Remediation

Upgrade `Ubuntu:24.04` `libssh` to version 0.10.6-2ubuntu0.2 or higher.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-8114
- https://access.redhat.com/security/cve/CVE-2025-8114
- https://bugzilla.redhat.com/show_bug.cgi?id=2383220
- https://git.libssh.org/projects/libssh.git/commit/?id=53ac23ded4cb2c5463f6c4cd1525331bd578812d
- https://www.libssh.org/security/advisories/CVE-2025-8114.txt
- https://git.libssh.org/projects/libssh.git/commit/?id=65f363c9

More about this vulnerability

## Information Exposure

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › gnupg2/dirmngr@2.4.4-2ubuntu17.3 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › gnupg2/gpg@2.4.4-2ubuntu17.3 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › gnupg2/gpg-agent@2.4.4-2ubuntu17.3 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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.0.20 › apt@2.8.3 › gnupg2/gpgv@2.4.4-2ubuntu17.3 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › gnupg2/gpg@2.4.4-2ubuntu17.3 › gnupg2/gpgconf@2.4.4-2ubuntu17.3 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › 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.11 › 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-2236
- https://access.redhat.com/errata/RHSA-2024:9404
- https://bugzilla.redhat.com/show_bug.cgi?id=2268268
- https://access.redhat.com/errata/RHSA-2025:3534
- https://access.redhat.com/errata/RHSA-2025:3530
- https://access.redhat.com/security/cve/CVE-2024-2236
- https://bugzilla.redhat.com/show_bug.cgi?id=2245218

More about this vulnerability

## Out-of-bounds Write

low severity

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

### Detailed paths

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

## 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-3219
- https://access.redhat.com/security/cve/CVE-2022-3219
- https://bugzilla.redhat.com/show_bug.cgi?id=2127010
- https://dev.gnupg.org/D556
- https://dev.gnupg.org/T5993
- https://marc.info/?l=oss-security&m=165696590211434&w=4
- https://security.netapp.com/advisory/ntap-20230324-0001/

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › glibc/libc-bin@2.39-0ubuntu8.6
- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › glibc/libc6@2.39-0ubuntu8.6

## 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-20013
- https://akkadia.org/drepper/SHA-crypt.txt
- https://pthree.org/2018/05/23/do-not-use-sha256crypt-sha512crypt-theyre-dangerous/
- https://twitter.com/solardiz/status/795601240151457793

More about this vulnerability

## CVE-2025-9086

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › git@1:2.43.0-1ubuntu7.3 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.6

## NVD Description

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

1. A cookie is set using the `secure` keyword for `https://target`
2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set
3. The same cookie name is set - but with just a slash as path (`path=&#39;/&#39;`). Since this site is not secure, the cookie should just be ignored.
4. A bug in the path comparison logic makes curl read outside a heap buffer boundary

The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path.

The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.

## Remediation

There is no fixed version for `Ubuntu:24.04` `curl`.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-9086
- https://curl.se/docs/CVE-2025-9086.html
- https://curl.se/docs/CVE-2025-9086.json
- https://hackerone.com/reports/3294999
- http://www.openwall.com/lists/oss-security/2025/09/10/1

More about this vulnerability

## CVE-2025-10148

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › git@1:2.43.0-1ubuntu7.3 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.6

## NVD Description

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

curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection.

A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy.

## Remediation

There is no fixed version for `Ubuntu:24.04` `curl`.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-10148
- https://curl.se/docs/CVE-2025-10148.html
- https://curl.se/docs/CVE-2025-10148.json
- https://hackerone.com/reports/3330839
- http://www.openwall.com/lists/oss-security/2025/09/10/2
- http://www.openwall.com/lists/oss-security/2025/09/10/3
- http://www.openwall.com/lists/oss-security/2025/09/10/4

More about this vulnerability

## CVE-2025-0167

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › git@1:2.43.0-1ubuntu7.3 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.6

## NVD Description

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

When asked to use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances.

This flaw only manifests itself if the netrc file has a `default` entry that omits both login and password. A rare circumstance.

## Remediation

There is no fixed version for `Ubuntu:24.04` `curl`.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-0167
- https://curl.se/docs/CVE-2025-0167.json
- https://hackerone.com/reports/2917232
- https://security.netapp.com/advisory/ntap-20250306-0008/
- https://curl.se/docs/CVE-2025-0167.html

More about this vulnerability

## Improper Input Validation

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v3.0.20 › coreutils@9.4-3ubuntu6.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: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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-2781
- https://security-tracker.debian.org/tracker/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://www.openwall.com/lists/oss-security/2016/02/28/2
- http://www.openwall.com/lists/oss-security/2016/02/28/3
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E

More about this vulnerability