# Snyk test report

June 16th 2024, 12:16:46 am (UTC+00:00)

Scanned the following paths:

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

21 known vulnerabilities
98 vulnerable dependency paths
2290 dependencies

## CVE-2020-22916

medium severity

- Manifest file: quay.io/argoproj/argocd:latest/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:24.04
- Vulnerable module: xz-utils/liblzma5
- Introduced through: docker-image|quay.io/argoproj/argocd@latest and xz-utils/liblzma5@5.6.1+really5.4.5-1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@latest › xz-utils/liblzma5@5.6.1+really5.4.5-1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › apt@2.7.14build2 › apt/libapt-pkg6.0t64@2.7.14build2 › xz-utils/liblzma5@5.6.1+really5.4.5-1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › dash@0.5.12-6ubuntu5 › dpkg@1.22.6ubuntu6 › xz-utils/liblzma5@5.6.1+really5.4.5-1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › apt@2.7.14build2 › adduser@3.137ubuntu1 › shadow/passwd@1:4.13+dfsg1-4ubuntu3 › pam/libpam-modules@1.5.3-5ubuntu5.1 › systemd/libsystemd0@255.4-1ubuntu8.1 › xz-utils/liblzma5@5.6.1+really5.4.5-1

## 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:24.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 vendor disputes the claims of "endless output" and "denial of service" because decompression of the 17,486 bytes always results in 114,881,179 bytes, which is often a reasonable size increase.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2020-22916
- https://github.com/snappyJack/CVE-request-XZ-5.2.5-has-denial-of-service-vulnerability
- https://tukaani.org/xz/
- https://bugzilla.redhat.com/show_bug.cgi?id=2234987
- https://bugzilla.suse.com/show_bug.cgi?id=1214590
- https://github.com/tukaani-project/xz/issues/61
- https://security-tracker.debian.org/tracker/CVE-2020-22916
- http://web.archive.org/web/20230918084612/https://github.com/snappyJack/CVE-request-XZ-5.2.5-has-denial-of-service-vulnerability

More about this vulnerability

## Information Exposure

medium severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@latest › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/dirmngr@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/gpg@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/gpg-agent@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › apt@2.7.14build2 › apt/libapt-pkg6.0t64@2.7.14build2 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › apt@2.7.14build2 › gnupg2/gpgv@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/gpg@2.4.4-2ubuntu17 › gnupg2/gpgconf@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › apt@2.7.14build2 › adduser@3.137ubuntu1 › shadow/passwd@1:4.13+dfsg1-4ubuntu3 › pam/libpam-modules@1.5.3-5ubuntu5.1 › systemd/libsystemd0@255.4-1ubuntu8.1 › 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/security/cve/CVE-2024-2236
- https://bugzilla.redhat.com/show_bug.cgi?id=2268268
- https://bugzilla.redhat.com/show_bug.cgi?id=2245218

More about this vulnerability

## CVE-2024-26462

medium severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › openssh/openssh-client@1:9.6p1-3ubuntu13 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › libssh/libssh-4@0.10.6-2build2 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › krb5/krb5-locales@1.20.1-6ubuntu2

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

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-26462
- https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_3.md
- https://security.netapp.com/advisory/ntap-20240415-0012/

More about this vulnerability

## LGPL-3.0 license

medium severity

- Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- Package Manager: golang
- Module: gopkg.in/retry.v1
- Introduced through: github.com/argoproj/argo-cd/v2@* and gopkg.in/retry.v1@v1.0.3

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › gopkg.in/retry.v1@v1.0.3

LGPL-3.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- 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

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

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › 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:latest/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- 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

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

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- 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

- Manifest file: quay.io/argoproj/argocd:latest/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- 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

## Release of Invalid Pointer or Reference

low severity

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

### Detailed paths

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

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `patch` package and not the `patch` package as distributed by `Ubuntu`. See `How to fix?` for `Ubuntu: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:latest/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:24.04
- Vulnerable module: patch
- Introduced through: docker-image|quay.io/argoproj/argocd@latest and patch@2.7.6-7build3

### Detailed paths

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

## NVD Description

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

low severity

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

### Detailed paths

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

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

Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions

Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service

This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation.

This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-2511
- https://github.com/openssl/openssl/commit/7e4d731b1c07201ad9374c1cd9ac5263bdf35bce
- https://github.com/openssl/openssl/commit/b52867a9f618bb955bed2a3ce3db4d4f97ed8e5d
- https://github.com/openssl/openssl/commit/e9d7083e241670332e0443da0f0d4ffb52829f08
- https://github.openssl.org/openssl/extended-releases/commit/5f8d25770ae6437db119dfc951e207271a326640
- https://www.openssl.org/news/secadv/20240408.txt
- http://www.openwall.com/lists/oss-security/2024/04/08/5
- https://security.netapp.com/advisory/ntap-20240503-0013/

More about this vulnerability

## CVE-2024-4603

low severity

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

### Detailed paths

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

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

Issue summary: Checking excessively long DSA keys or parameters may be very slow.

Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (`p` parameter) is too large.

Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks.

An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable.

Also vulnerable are the OpenSSL pkey and pkeyparam command line applications when using the `-check` option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-4603
- https://github.com/openssl/openssl/commit/3559e868e58005d15c6013a0c1fd832e51c73397
- https://github.com/openssl/openssl/commit/53ea06486d296b890d565fb971b2764fcd826e7e
- https://github.com/openssl/openssl/commit/9c39b3858091c152f52513c066ff2c5a47969f0d
- https://github.com/openssl/openssl/commit/da343d0605c826ef197aceedc67e8e04f065f740
- https://www.openssl.org/news/secadv/20240516.txt
- http://www.openwall.com/lists/oss-security/2024/05/16/2

More about this vulnerability

## CVE-2024-4741

low severity

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

### Detailed paths

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

## NVD Description

This vulnerability has not been analyzed by NVD yet.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-4741

More about this vulnerability

## CVE-2024-26458

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › openssh/openssh-client@1:9.6p1-3ubuntu13 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › libssh/libssh-4@0.10.6-2build2 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › krb5/krb5-locales@1.20.1-6ubuntu2

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

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-26458
- https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_1.md
- https://security.netapp.com/advisory/ntap-20240415-0010/

More about this vulnerability

## CVE-2024-26461

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2 › krb5/libk5crypto3@1.20.1-6ubuntu2 › krb5/libkrb5support0@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2 › krb5/libkrb5-3@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › openssh/openssh-client@1:9.6p1-3ubuntu13 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › curl/libcurl3t64-gnutls@8.5.0-2ubuntu10.1 › libssh/libssh-4@0.10.6-2build2 › krb5/libgssapi-krb5-2@1.20.1-6ubuntu2
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › krb5/krb5-locales@1.20.1-6ubuntu2

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

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-26461
- https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_2.md
- https://security.netapp.com/advisory/ntap-20240415-0011/

More about this vulnerability

## Out-of-bounds Write

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/gpgv@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › apt@2.7.14build2 › gnupg2/gpgv@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/dirmngr@2.4.4-2ubuntu17 › gnupg2/gpgconf@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/gpg-agent@2.4.4-2ubuntu17 › gnupg2/gpgconf@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/gpg@2.4.4-2ubuntu17 › gnupg2/gpgconf@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/dirmngr@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/gpg@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › gnupg2/gpg-agent@2.4.4-2ubuntu17

## 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:latest/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:24.04
- Vulnerable module: glibc/libc-bin
- Introduced through: docker-image|quay.io/argoproj/argocd@latest and glibc/libc-bin@2.39-0ubuntu8.2

### Detailed paths

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

## 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://twitter.com/solardiz/status/795601240151457793
- https://pthree.org/2018/05/23/do-not-use-sha256crypt-sha512crypt-theyre-dangerous/
- https://akkadia.org/drepper/SHA-crypt.txt

More about this vulnerability

## Improper Input Validation

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1 › git/git-man@1:2.43.0-1ubuntu7.1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git@1:2.43.0-1ubuntu7.1
- Introduced through: docker-image|quay.io/argoproj/argocd@latest › git-lfs@3.4.1-1 › git@1:2.43.0-1ubuntu7.1

## NVD Description

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-1000021
- https://security-tracker.debian.org/tracker/CVE-2018-1000021
- http://www.batterystapl.es/2018/01/security-implications-of-ansi-escape.html

More about this vulnerability

## Improper Input Validation

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@latest › coreutils@9.4-3ubuntu6

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