# Snyk test report

September 17th 2023, 12:19:32 am (UTC+00:00)

Scanned the following paths:

- quay.io/argoproj/argocd:v2.8.4/argoproj/argocd (deb)
- quay.io/argoproj/argocd:v2.8.4/argoproj/argo-cd/v2 (gomodules)
- quay.io/argoproj/argocd:v2.8.4/kustomize/kustomize/v5 (gomodules)
- quay.io/argoproj/argocd:v2.8.4/helm/v3 (gomodules)
- quay.io/argoproj/argocd:v2.8.4/git-lfs/git-lfs (gomodules)

27 known vulnerabilities
102 vulnerable dependency paths
2116 dependencies

## Directory Traversal

high severity

- Package Manager: golang
- Vulnerable module: github.com/cyphar/filepath-securejoin
- Introduced through: helm.sh/helm/v3@* and github.com/cyphar/filepath-securejoin@v0.2.3

### Detailed paths

- Introduced through: helm.sh/helm/v3@* › github.com/cyphar/filepath-securejoin@v0.2.3

## Overview

Affected versions of this package are vulnerable to Directory Traversal via the `filepath.FromSlash()` function, allwoing attackers to generate paths that were outside of the provided `rootfs`.

Note: This vulnerability is only exploitable on Windows OS.

## Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

- Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

`st` is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the `public` route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

    curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note `%2e` is the URL encoded version of `.` (dot).

- Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as `Zip-Slip`.

One way to achieve this is by using a malicious `zip` archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a `zip` archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in `/root/.ssh/` overwriting the `authorized_keys` file:

    2018-04-15 22:04:29 .....           19           19  good.txt
            2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

## Remediation

Upgrade `github.com/cyphar/filepath-securejoin` to version 0.2.4 or higher.

## References

- GitHub Commit
- GitHub PR
- GitHub Release

More about this vulnerability

## CVE-2020-22916

medium severity

- Package Manager: ubuntu:22.04
- Vulnerable module: xz-utils/liblzma5
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and xz-utils/liblzma5@5.2.5-2ubuntu1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › xz-utils/liblzma5@5.2.5-2ubuntu1

## NVD Description

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

An issue discovered in XZ 5.2.5 allows attackers to cause a denial of service via decompression of a crafted file. NOTE: the software maintainers are unable to reproduce this as of 2023-09-12 because the example crafted file is temporarily offline.

## Remediation

There is no fixed version for `Ubuntu:22.04` `xz-utils`.

## References

- ADVISORY
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## Out-of-bounds Write

medium severity

- Package Manager: ubuntu:22.04
- Vulnerable module: perl/perl-modules-5.34
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4, git@1:2.34.1-1ubuntu1.10 and others

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › perl@5.34.0-3ubuntu1.2 › perl/perl-modules-5.34@5.34.0-3ubuntu1.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › perl@5.34.0-3ubuntu1.2 › perl/libperl5.34@5.34.0-3ubuntu1.2 › perl/perl-modules-5.34@5.34.0-3ubuntu1.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › perl@5.34.0-3ubuntu1.2 › perl/libperl5.34@5.34.0-3ubuntu1.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › perl@5.34.0-3ubuntu1.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › perl/perl-base@5.34.0-3ubuntu1.2

## NVD Description

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

In Perl 5.34.0, function S_find_uninit_var in sv.c has a stack-based crash that can lead to remote code execution or local privilege escalation.

## Remediation

There is no fixed version for `Ubuntu:22.04` `perl`.

## References

- ADVISORY
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## Access of Uninitialized Pointer

medium severity

- Package Manager: ubuntu:22.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and krb5/libk5crypto3@1.19.2-2ubuntu0.2

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › krb5/libk5crypto3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2 › krb5/libk5crypto3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2 › krb5/libkrb5-3@1.19.2-2ubuntu0.2 › krb5/libk5crypto3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › krb5/libkrb5-3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2 › krb5/libkrb5-3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › openssh/openssh-client@1:8.9p1-3ubuntu0.3 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › curl/libcurl3-gnutls@7.81.0-1ubuntu1.13 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › curl/libcurl3-gnutls@7.81.0-1ubuntu1.13 › libssh/libssh-4@0.9.6-2ubuntu0.22.04.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › krb5/libkrb5support0@1.19.2-2ubuntu0.2

## NVD Description

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

lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.

## Remediation

There is no fixed version for `Ubuntu:22.04` `krb5`.

## References

- ADVISORY
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## MPL-2.0 license

medium severity

- Package Manager: golang
- Module: github.com/r3labs/diff
- Introduced through: github.com/argoproj/argo-cd/v2@* and github.com/r3labs/diff@v1.1.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › github.com/r3labs/diff@v1.1.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Package Manager: golang
- Module: github.com/hashicorp/go-version
- Introduced through: github.com/argoproj/argo-cd/v2@* and github.com/hashicorp/go-version@v1.2.1

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Package Manager: golang
- Module: github.com/hashicorp/go-retryablehttp
- Introduced through: github.com/argoproj/argo-cd/v2@* and github.com/hashicorp/go-retryablehttp@v0.7.4

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › github.com/hashicorp/go-retryablehttp@v0.7.4

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- 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

- Package Manager: golang
- Module: github.com/hashicorp/go-cleanhttp
- Introduced through: github.com/argoproj/argo-cd/v2@* and github.com/hashicorp/go-cleanhttp@v0.5.2

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Package Manager: golang
- Module: github.com/gosimple/slug
- Introduced through: github.com/argoproj/argo-cd/v2@* and github.com/gosimple/slug@v1.13.1

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › github.com/gosimple/slug@v1.13.1

MPL-2.0 license

More about this vulnerability

## CVE-2022-46908

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4, gnupg2/gpg@2.2.27-3ubuntu2.1 and others

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gpg@2.2.27-3ubuntu2.1 › sqlite3/libsqlite3-0@3.37.2-2ubuntu0.1

## NVD Description

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

SQLite through 3.40.0, when relying on --safe for execution of an untrusted CLI script, does not properly implement the azProhibitedFunctions protection mechanism, and instead allows UDF functions such as WRITEFILE.

## Remediation

There is no fixed version for `Ubuntu:22.04` `sqlite3`.

## References

- ADVISORY
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## Arbitrary Code Injection

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: shadow/passwd
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and shadow/passwd@1:4.8.1-2ubuntu2.1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › shadow/passwd@1:4.8.1-2ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › openssh/openssh-client@1:8.9p1-3ubuntu0.3 › shadow/passwd@1:4.8.1-2ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › shadow/login@1:4.8.1-2ubuntu2.1

## NVD Description

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

In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.

## Remediation

There is no fixed version for `Ubuntu:22.04` `shadow`.

## References

- ADVISORY
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## Out-of-bounds Write

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: procps/libprocps8
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and procps/libprocps8@2:3.3.17-6ubuntu2

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › procps/libprocps8@2:3.3.17-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › procps@2:3.3.17-6ubuntu2 › procps/libprocps8@2:3.3.17-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › procps@2:3.3.17-6ubuntu2

## NVD Description

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

Under some circumstances, this weakness allows a user who has access to run the “ps” utility on a machine, the ability to write almost unlimited amounts of unfiltered data into the process heap.

## Remediation

There is no fixed version for `Ubuntu:22.04` `procps`.

## References

- ADVISORY
- trellixpsirt@trellix.com
- trellixpsirt@trellix.com

More about this vulnerability

## Uncontrolled Recursion

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: pcre3/libpcre3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › grep@3.7-1build1 › pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1

## NVD Description

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

In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.

## Remediation

There is no fixed version for `Ubuntu:22.04` `pcre3`.

## References

- ADVISORY
- CVE Details
- Debian Security Tracker
- MLIST
- OSS security Advisory
- Security Focus
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## Release of Invalid Pointer or Reference

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: patch
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and patch@2.7.6-7build2

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › patch@2.7.6-7build2

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `patch` package and not the `patch` package as distributed by `Ubuntu:22.04`. See `How to fix?` for `Ubuntu:22.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:22.04` `patch`.

## References

- ADVISORY
- MISC

More about this vulnerability

## Double Free

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: patch
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and patch@2.7.6-7build2

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › patch@2.7.6-7build2

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `patch` package and not the `patch` package as distributed by `Ubuntu:22.04`. See `How to fix?` for `Ubuntu:22.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:22.04` `patch`.

## References

- ADVISORY
- CVE Details
- Debian Security Tracker
- Gentoo Security Advisory
- MISC
- REDHAT
- Security Focus

More about this vulnerability

## Improper Authentication

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: openssl/libssl3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and openssl/libssl3@3.0.2-0ubuntu1.10

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › openssl/libssl3@3.0.2-0ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › cyrus-sasl2/libsasl2-modules@2.1.27+dfsg2-3ubuntu1.2 › openssl/libssl3@3.0.2-0ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › libfido2/libfido2-1@1.10.0-1 › openssl/libssl3@3.0.2-0ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › openssh/openssh-client@1:8.9p1-3ubuntu0.3 › openssl/libssl3@3.0.2-0ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › ca-certificates@20230311ubuntu0.22.04.1 › openssl@3.0.2-0ubuntu1.10 › openssl/libssl3@3.0.2-0ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › curl/libcurl3-gnutls@7.81.0-1ubuntu1.13 › libssh/libssh-4@0.9.6-2ubuntu0.22.04.1 › openssl/libssl3@3.0.2-0ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2 › krb5/libkrb5-3@1.19.2-2ubuntu0.2 › openssl/libssl3@3.0.2-0ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › openssl@3.0.2-0ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › ca-certificates@20230311ubuntu0.22.04.1 › openssl@3.0.2-0ubuntu1.10

## NVD Description

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

Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence.

Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be mislead by removing adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications.

The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated.

As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.

## Remediation

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

## References

- ADVISORY
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org

More about this vulnerability

## CVE-2023-28531

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: openssh/openssh-client
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and openssh/openssh-client@1:8.9p1-3ubuntu0.3

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › openssh/openssh-client@1:8.9p1-3ubuntu0.3

## NVD Description

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

ssh-add in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination constraints. The earliest affected version is 8.9.

## Remediation

There is no fixed version for `Ubuntu:22.04` `openssh`.

## References

- ADVISORY
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## NULL Pointer Dereference

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: openldap/libldap-2.5-0
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4, gnupg2/dirmngr@2.2.27-3ubuntu2.1 and others

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/dirmngr@2.2.27-3ubuntu2.1 › openldap/libldap-2.5-0@2.5.16+dfsg-0ubuntu0.22.04.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › curl/libcurl3-gnutls@7.81.0-1ubuntu1.13 › openldap/libldap-2.5-0@2.5.16+dfsg-0ubuntu0.22.04.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › openldap/libldap-common@2.5.16+dfsg-0ubuntu0.22.04.1

## NVD Description

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

A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.

## Remediation

There is no fixed version for `Ubuntu:22.04` `openldap`.

## References

- ADVISORY
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com

More about this vulnerability

## Resource Exhaustion

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: libzstd/libzstd1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and libzstd/libzstd1@1.4.8+dfsg-3build1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › libzstd/libzstd1@1.4.8+dfsg-3build1

## NVD Description

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

A vulnerability was found in zstd v1.4.10, where an attacker can supply empty string as an argument to the command line tool to cause buffer overrun.

## Remediation

There is no fixed version for `Ubuntu:22.04` `libzstd`.

## References

- ADVISORY
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com

More about this vulnerability

## Integer Overflow or Wraparound

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and krb5/libk5crypto3@1.19.2-2ubuntu0.2

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › krb5/libk5crypto3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2 › krb5/libk5crypto3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2 › krb5/libkrb5-3@1.19.2-2ubuntu0.2 › krb5/libk5crypto3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › krb5/libkrb5-3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2 › krb5/libkrb5-3@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › openssh/openssh-client@1:8.9p1-3ubuntu0.3 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › curl/libcurl3-gnutls@7.81.0-1ubuntu1.13 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › curl/libcurl3-gnutls@7.81.0-1ubuntu1.13 › libssh/libssh-4@0.9.6-2ubuntu0.22.04.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.1 › pam/libpam-modules@1.4.0-11ubuntu2.3 › libnsl/libnsl2@1.3.0-2build2 › libtirpc/libtirpc3@1.3.2-2ubuntu0.1 › krb5/libgssapi-krb5-2@1.19.2-2ubuntu0.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › krb5/libkrb5support0@1.19.2-2ubuntu0.2

## NVD Description

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

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

## Remediation

There is no fixed version for `Ubuntu:22.04` `krb5`.

## References

- CVE Details
- Debian Security Tracker
- GitHub Additional Information
- MLIST
- Ubuntu CVE Tracker

More about this vulnerability

## Out-of-bounds Write

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: gnupg2/gpgv
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and gnupg2/gpgv@2.2.27-3ubuntu2.1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gpgv@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › apt@2.4.10 › gnupg2/gpgv@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpgv@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/dirmngr@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gpg@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpgsm@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/dirmngr@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/dirmngr@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.1 › gnupg2/dirmngr@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg-l10n@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gnupg-l10n@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg-utils@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gnupg-utils@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gpg@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.1 › gnupg2/gpg@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-server@2.2.27-3ubuntu2.1 › gnupg2/gpg@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-server@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gpg-wks-server@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-server@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gpgsm@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpgsm@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gnupg2/gnupg@2.2.27-3ubuntu2.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:22.04`. See `How to fix?` for `Ubuntu:22.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:22.04` `gnupg2`.

## References

- ADVISORY
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com
- secalert@redhat.com

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: glibc/libc-bin
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and glibc/libc-bin@2.35-0ubuntu3.3

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › glibc/libc-bin@2.35-0ubuntu3.3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › glibc/libc6@2.35-0ubuntu3.3

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `glibc` package and not the `glibc` package as distributed by `Ubuntu:22.04`. See `How to fix?` for `Ubuntu:22.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:22.04` `glibc`.

## References

- ADVISORY
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## Improper Input Validation

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: git/git-man
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4, git@1:2.34.1-1ubuntu1.10 and others

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10 › git/git-man@1:2.34.1-1ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git@1:2.34.1-1ubuntu1.10
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › git-lfs@3.0.2-1ubuntu0.2 › git@1:2.34.1-1ubuntu1.10

## NVD Description

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

GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).

## Remediation

There is no fixed version for `Ubuntu:22.04` `git`.

## References

- ADVISORY
- Debian Security Tracker
- http://www.batterystapl.es/2018/01/security-implications-of-ansi-escape.html

More about this vulnerability

## Uncontrolled Recursion

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: gcc-12/libstdc++6
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › apt@2.4.10 › gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › apt@2.4.10 › apt/libapt-pkg6.0@2.4.10 › gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gcc-12/gcc-12-base@12.3.0-1ubuntu1~22.04
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › gcc-12/libgcc-s1@12.3.0-1ubuntu1~22.04

## NVD Description

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

libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.

## Remediation

There is no fixed version for `Ubuntu:22.04` `gcc-12`.

## References

- ADVISORY
- cve@mitre.org
- cve@mitre.org
- cve@mitre.org

More about this vulnerability

## Improper Input Validation

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: coreutils
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and coreutils@8.32-4.1ubuntu1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › coreutils@8.32-4.1ubuntu1

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `coreutils` package and not the `coreutils` package as distributed by `Ubuntu:22.04`. See `How to fix?` for `Ubuntu:22.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:22.04` `coreutils`.

## References

- ADVISORY
- Debian Security Tracker
- MLIST
- OSS security Advisory
- OSS security Advisory

More about this vulnerability

## Out-of-bounds Write

low severity

- Package Manager: ubuntu:22.04
- Vulnerable module: bash
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 and bash@5.1-6ubuntu1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.8.4 › bash@5.1-6ubuntu1

## NVD Description

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

A flaw was found in the bash package, where a heap-buffer overflow can occur in valid parameter_transform. This issue may lead to memory problems.

## Remediation

There is no fixed version for `Ubuntu:22.04` `bash`.

## References

- ADVISORY
- secalert@redhat.com

More about this vulnerability