# Snyk test report

September 8th 2024, 12:26:46 am (UTC+00:00)

Scanned the following paths:

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

33 known vulnerabilities
235 vulnerable dependency paths
2278 dependencies

## Allocation of Resources Without Limits or Throttling

high severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: golang.org/x/net/http2
- Introduced through: github.com/argoproj/argo-cd/v2@* and golang.org/x/net/http2@v0.19.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › golang.org/x/net/http2@v0.19.0
- Introduced through: helm.sh/helm/v3@* › golang.org/x/net/http2@v0.17.0

## Overview

golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling when reading header data from `CONTINUATION` frames. As part of the HPACK flow, all incoming `HEADERS` and `CONTINUATION` frames are read even if their payloads exceed `MaxHeaderBytes` and will be discarded. An attacker can send excessive data over a connection to render it unresponsive.

## Remediation

Upgrade `golang.org/x/net/http2` to version 0.23.0 or higher.

## References

- Github Commit
- GitHub Commit
- GitHub Issue
- Go Advisory

More about this vulnerability

## CVE-2024-41996

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: openssl/libssl3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and openssl/libssl3@3.0.2-0ubuntu1.16

### Detailed paths

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

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

## CVE-2024-6119

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: openssl/libssl3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and openssl/libssl3@3.0.2-0ubuntu1.16

### Detailed paths

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

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

Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.

Impact summary: Abnormal termination of an application can a cause a denial of service.

Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an `otherName` subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program.

Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

## Remediation

Upgrade `Ubuntu:22.04` `openssl` to version 3.0.2-0ubuntu1.18 or higher.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-6119
- https://github.com/openssl/openssl/commit/05f360d9e849a1b277db628f1f13083a7f8dd04f
- https://github.com/openssl/openssl/commit/06d1dc3fa96a2ba5a3e22735a033012aadc9f0d6
- https://github.com/openssl/openssl/commit/621f3729831b05ee828a3203eddb621d014ff2b2
- https://github.com/openssl/openssl/commit/7dfcee2cd2a63b2c64b9b4b0850be64cb695b0a0
- https://openssl-library.org/news/secadv/20240903.txt

More about this vulnerability

## Information Exposure

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: libgcrypt20
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and libgcrypt20@1.9.4-3ubuntu3

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/dirmngr@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gpg@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › apt/libapt-pkg6.0@2.4.12 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › gnupg2/gpgv@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gpg@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gnupg-utils@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-wks-server@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpgsm@2.2.27-3ubuntu2.1 › libgcrypt20@1.9.4-3ubuntu3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › apt/libapt-pkg6.0@2.4.12 › systemd/libsystemd0@249.11-0ubuntu3.12 › libgcrypt20@1.9.4-3ubuntu3

## 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:22.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:22.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:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and krb5/libk5crypto3@1.19.2-2ubuntu0.3

### Detailed paths

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

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

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:22.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

## CVE-2024-37371

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and krb5/libk5crypto3@1.19.2-2ubuntu0.3

### Detailed paths

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

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

In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.

## Remediation

Upgrade `Ubuntu:22.04` `krb5` to version 1.19.2-2ubuntu0.4 or higher.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-37371
- https://github.com/krb5/krb5/commit/55fbf435edbe2e92dd8101669b1ce7144bc96fef
- https://web.mit.edu/kerberos/www/advisories/

More about this vulnerability

## CVE-2024-37370

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and krb5/libk5crypto3@1.19.2-2ubuntu0.3

### Detailed paths

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

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

In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.

## Remediation

Upgrade `Ubuntu:22.04` `krb5` to version 1.19.2-2ubuntu0.4 or higher.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-37370
- https://github.com/krb5/krb5/commit/55fbf435edbe2e92dd8101669b1ce7144bc96fef
- https://web.mit.edu/kerberos/www/advisories/

More about this vulnerability

## Denial of Service (DoS)

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: github.com/rs/cors
- Introduced through: github.com/argoproj/argo-cd/v2@* and github.com/rs/cors@v1.9.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › github.com/rs/cors@v1.9.0

## Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) through the processing of malicious preflight requests that include a `Access-Control-Request-Headers` header with excessive commas. An attacker can induce excessive memory consumption and potentially crash the server by sending specially crafted requests.

## PoC

            func BenchmarkPreflightAdversarialACRH(b *testing.B) {
                resps := makeFakeResponses(b.N)
                req, _ := http.NewRequest(http.MethodOptions, dummyEndpoint, nil)
                req.Header.Add(headerOrigin, dummyOrigin)
                req.Header.Add(headerACRM, http.MethodGet)
                req.Header[headerACRH] = adversarialACRH
                handler := Default().Handler(testHandler)

                b.ReportAllocs()
                b.ResetTimer()
                for i := 0; i < b.N; i++ {
                    handler.ServeHTTP(resps[i], req)
                }
            }

            var adversarialACRH []string

            func init() { // populates adversarialACRH
                n := int(math.Floor(math.Sqrt(http.DefaultMaxHeaderBytes)))
                commas := strings.Repeat(",", n)
                res := make([]string, n)
                for i := range res {
                    res[i] = commas
                }
                adversarialACRH = res
            }

## 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 `github.com/rs/cors` to version 1.11.0 or higher.

## References

- GitHub Commit
- GitHub Issue
- GitHub PR

More about this vulnerability

## Insertion of Sensitive Information into Log File

medium severity

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

## Overview

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File due to not sanitizing urls when writing them to the log file. This could lead to an attacker writing sensitive HTTP basic auth credentials to the log file.

## Remediation

Upgrade `github.com/hashicorp/go-retryablehttp` to version 0.7.7 or higher.

## References

- GitHub Commit
- HashiCorp Discuss

More about this vulnerability

## Integer Overflow or Wraparound

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: expat/libexpat1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16, git@1:2.34.1-1ubuntu1.11 and others

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › git@1:2.34.1-1ubuntu1.11 › expat/libexpat1@2.4.7-1ubuntu0.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:22.04` relevant fixed versions and status.

An issue was discovered in libexpat before 2.6.3. dtdCopy in xmlparse.c can have an integer overflow for nDefaultAtts on 32-bit platforms (where UINT_MAX equals SIZE_MAX).

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-45491
- https://github.com/libexpat/libexpat/issues/888
- https://github.com/libexpat/libexpat/pull/891

More about this vulnerability

## XML External Entity (XXE) Injection

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: expat/libexpat1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16, git@1:2.34.1-1ubuntu1.11 and others

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › git@1:2.34.1-1ubuntu1.11 › expat/libexpat1@2.4.7-1ubuntu0.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:22.04` relevant fixed versions and status.

An issue was discovered in libexpat before 2.6.3. xmlparse.c does not reject a negative length for XML_ParseBuffer.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-45490
- https://github.com/libexpat/libexpat/issues/887
- https://github.com/libexpat/libexpat/pull/890

More about this vulnerability

## Integer Overflow or Wraparound

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: expat/libexpat1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16, git@1:2.34.1-1ubuntu1.11 and others

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › git@1:2.34.1-1ubuntu1.11 › expat/libexpat1@2.4.7-1ubuntu0.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:22.04` relevant fixed versions and status.

An issue was discovered in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX).

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-45492
- https://github.com/libexpat/libexpat/issues/889
- https://github.com/libexpat/libexpat/pull/892

More about this vulnerability

## Out-of-bounds Read

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: curl/libcurl3-gnutls
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16, git@1:2.34.1-1ubuntu1.11 and others

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › git@1:2.34.1-1ubuntu1.11 › curl/libcurl3-gnutls@7.81.0-1ubuntu1.16

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

libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the time fraction, leading to a `strlen()` getting performed on a pointer to a heap buffer area that is not (purposely) null terminated.

This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when CURLINFO_CERTINFO is used.

## Remediation

Upgrade `Ubuntu:22.04` `curl` to version 7.81.0-1ubuntu1.17 or higher.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-7264
- http://www.openwall.com/lists/oss-security/2024/07/31/1
- https://curl.se/docs/CVE-2024-7264.html
- https://curl.se/docs/CVE-2024-7264.json
- https://hackerone.com/reports/2629968

More about this vulnerability

## CVE-2023-7008

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: systemd/libsystemd0
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and systemd/libsystemd0@249.11-0ubuntu3.12

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › systemd/libsystemd0@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › systemd/libsystemd0@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › procps/libprocps8@2:3.3.17-6ubuntu2.1 › systemd/libsystemd0@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › util-linux@2.37.2-4ubuntu3.4 › systemd/libsystemd0@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › util-linux/bsdutils@1:2.37.2-4ubuntu3.4 › systemd/libsystemd0@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › apt/libapt-pkg6.0@2.4.12 › systemd/libsystemd0@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › systemd/libudev1@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › libfido2/libfido2-1@1.10.0-1 › systemd/libudev1@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › util-linux@2.37.2-4ubuntu3.4 › systemd/libudev1@249.11-0ubuntu3.12
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › apt/libapt-pkg6.0@2.4.12 › systemd/libudev1@249.11-0ubuntu3.12

## NVD Description

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

A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-7008
- https://access.redhat.com/security/cve/CVE-2023-7008
- https://bugzilla.redhat.com/show_bug.cgi?id=2222261
- https://bugzilla.redhat.com/show_bug.cgi?id=2222672
- https://github.com/systemd/systemd/issues/25676
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QHNBXGKJWISJETTTDTZKTBFIBJUOSLKL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4GMDEG5PKONWNHOEYSUDRT6JEOISRMN2/
- https://access.redhat.com/errata/RHSA-2024:2463
- https://access.redhat.com/errata/RHSA-2024:3203

More about this vulnerability

## Arbitrary Code Injection

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › shadow/passwd@1:4.8.1-2ubuntu2.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › adduser@3.118ubuntu5 › shadow/passwd@1:4.8.1-2ubuntu2.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › openssh/openssh-client@1:8.9p1-3ubuntu0.10 › shadow/passwd@1:4.8.1-2ubuntu2.2
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › shadow/login@1:4.8.1-2ubuntu2.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: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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-29383
- https://github.com/shadow-maint/shadow/commit/e5905c4b84d4fb90aefcd96ee618411ebfac663d
- https://github.com/shadow-maint/shadow/pull/687
- https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/cve-2023-29383-abusing-linux-chfn-to-misrepresent-etc-passwd/
- https://www.trustwave.com/en-us/resources/security-resources/security-advisories/?fid=31797

More about this vulnerability

## Uncontrolled Recursion

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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`. 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-11164
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11164
- https://security-tracker.debian.org/tracker/CVE-2017-11164
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://openwall.com/lists/oss-security/2017/07/11/3
- http://www.securityfocus.com/bid/99575
- http://www.openwall.com/lists/oss-security/2023/04/11/1
- http://www.openwall.com/lists/oss-security/2023/04/12/1
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E

More about this vulnerability

## Release of Invalid Pointer or Reference

low severity

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

### Detailed paths

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

- 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:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: patch
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and patch@2.7.6-7build2

### Detailed paths

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

- 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:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: openssl/libssl3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and openssl/libssl3@3.0.2-0ubuntu1.16

### Detailed paths

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

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

Upgrade `Ubuntu:22.04` `openssl` to version 3.0.2-0ubuntu1.17 or higher.

## 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:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: openssl/libssl3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and openssl/libssl3@3.0.2-0ubuntu1.16

### Detailed paths

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

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

Upgrade `Ubuntu:22.04` `openssl` to version 3.0.2-0ubuntu1.17 or higher.

## 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
- https://security.netapp.com/advisory/ntap-20240621-0001/

More about this vulnerability

## CVE-2024-4741

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: openssl/libssl3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and openssl/libssl3@3.0.2-0ubuntu1.16

### Detailed paths

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

## NVD Description

This vulnerability has not been analyzed by NVD yet.

## Remediation

Upgrade `Ubuntu:22.04` `openssl` to version 3.0.2-0ubuntu1.17 or higher.

## References

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

More about this vulnerability

## CVE-2024-5535

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: openssl/libssl3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and openssl/libssl3@3.0.2-0ubuntu1.16

### Detailed paths

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

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

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer.

Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application.

The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists).

This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem.

In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur.

This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.

## Remediation

Upgrade `Ubuntu:22.04` `openssl` to version 3.0.2-0ubuntu1.17 or higher.

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-5535
- https://github.com/openssl/openssl/commit/4ada436a1946cbb24db5ab4ca082b69c1bc10f37
- https://github.com/openssl/openssl/commit/99fb785a5f85315b95288921a321a935ea29a51e
- https://github.com/openssl/openssl/commit/cf6f91f6121f4db167405db2f0de410a456f260c
- https://github.com/openssl/openssl/commit/e86ac436f0bd54d4517745483e2315650fae7b2c
- https://github.openssl.org/openssl/extended-releases/commit/9947251413065a05189a63c9b7a6c1d4e224c21c
- https://github.openssl.org/openssl/extended-releases/commit/b78ec0824da857223486660177d3b1f255c65d87
- https://www.openssl.org/news/secadv/20240627.txt
- http://www.openwall.com/lists/oss-security/2024/06/27/1
- http://www.openwall.com/lists/oss-security/2024/06/28/4
- https://security.netapp.com/advisory/ntap-20240712-0005/

More about this vulnerability

## CVE-2023-50495

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: ncurses/libtinfo6
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and ncurses/libtinfo6@6.3-2ubuntu0.1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › bash@5.1-6ubuntu1.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libncursesw6@6.3-2ubuntu0.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › less@590-1ubuntu0.22.04.3 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › libedit/libedit2@3.1-20210910-1build1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libncurses6@6.3-2ubuntu0.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/ncurses-bin@6.3-2ubuntu0.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › procps@2:3.3.17-6ubuntu2.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › util-linux@2.37.2-4ubuntu3.4 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gpg@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1 › readline/libreadline8@8.1.2-1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1 › pinentry/pinentry-curses@1.1.1-1build2 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libncursesw6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › procps@2:3.3.17-6ubuntu2.1 › ncurses/libncursesw6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1 › pinentry/pinentry-curses@1.1.1-1build2 › ncurses/libncursesw6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libncurses6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › procps@2:3.3.17-6ubuntu2.1 › ncurses/libncurses6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/ncurses-base@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/ncurses-bin@6.3-2ubuntu0.1

## NVD Description

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

NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-50495
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00020.html
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00029.html
- https://security.netapp.com/advisory/ntap-20240119-0008/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/

More about this vulnerability

## CVE-2023-45918

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: ncurses/libtinfo6
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and ncurses/libtinfo6@6.3-2ubuntu0.1

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › bash@5.1-6ubuntu1.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libncursesw6@6.3-2ubuntu0.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › less@590-1ubuntu0.22.04.3 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › libedit/libedit2@3.1-20210910-1build1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libncurses6@6.3-2ubuntu0.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/ncurses-bin@6.3-2ubuntu0.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › procps@2:3.3.17-6ubuntu2.1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › util-linux@2.37.2-4ubuntu3.4 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gpg@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1 › readline/libreadline8@8.1.2-1 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1 › pinentry/pinentry-curses@1.1.1-1build2 › ncurses/libtinfo6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libncursesw6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › procps@2:3.3.17-6ubuntu2.1 › ncurses/libncursesw6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1 › pinentry/pinentry-curses@1.1.1-1build2 › ncurses/libncursesw6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/libncurses6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › procps@2:3.3.17-6ubuntu2.1 › ncurses/libncurses6@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/ncurses-base@6.3-2ubuntu0.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › ncurses/ncurses-bin@6.3-2ubuntu0.1

## NVD Description

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

ncurses 6.4-20230610 has a NULL pointer dereference in tgetstr in tinfo/lib_termcap.c.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-45918
- https://lists.gnu.org/archive/html/bug-ncurses/2023-06/msg00005.html
- https://security.netapp.com/advisory/ntap-20240315-0006/

More about this vulnerability

## Resource Exhaustion

low severity

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

### Detailed paths

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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-4899
- https://github.com/facebook/zstd/issues/3200
- https://security.netapp.com/advisory/ntap-20230725-0005/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C63HAGVLQA6FJNDCHR7CNZZL6VSLILB2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JEHRBBYYTPA4DETOM5XAKGCP37NUTLOA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QYLDK6ODVC4LJSDULLX6Q2YHTFOWABCN/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C63HAGVLQA6FJNDCHR7CNZZL6VSLILB2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JEHRBBYYTPA4DETOM5XAKGCP37NUTLOA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QYLDK6ODVC4LJSDULLX6Q2YHTFOWABCN/

More about this vulnerability

## Integer Overflow or Wraparound

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and krb5/libk5crypto3@1.19.2-2ubuntu0.3

### Detailed paths

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

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

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

- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5709
- https://security-tracker.debian.org/tracker/CVE-2018-5709
- https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-5709
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E

More about this vulnerability

## CVE-2024-26461

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and krb5/libk5crypto3@1.19.2-2ubuntu0.3

### Detailed paths

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

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

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:22.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

## CVE-2024-26458

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and krb5/libk5crypto3@1.19.2-2ubuntu0.3

### Detailed paths

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

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

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:22.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

## Out-of-bounds Write

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gpgv@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › gnupg2/gpgv@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpgv@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/dirmngr@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gpg@2.2.27-3ubuntu2.1 › gnupg2/gpgconf@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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.10.16 › 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.10.16 › gnupg2/dirmngr@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/dirmngr@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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.10.16 › gnupg2/gnupg-l10n@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gnupg-l10n@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg-utils@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gnupg-utils@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gpg@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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.10.16 › 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.10.16 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpg-agent@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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.10.16 › 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.10.16 › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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.10.16 › gnupg2/gpg-wks-server@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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.10.16 › gnupg2/gpgsm@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gnupg2/gnupg@2.2.27-3ubuntu2.1 › gnupg2/gpgsm@2.2.27-3ubuntu2.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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`. 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

- 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:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: glibc/libc-bin
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and glibc/libc-bin@2.35-0ubuntu3.8

### Detailed paths

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

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

- 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

## Improper Input Validation

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: git/git-man
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16, git@1:2.34.1-1ubuntu1.11 and others

### Detailed paths

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

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

- 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

## Uncontrolled Recursion

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › apt@2.4.12 › apt/libapt-pkg6.0@2.4.12 › gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › gcc-12/gcc-12-base@12.3.0-1ubuntu1~22.04
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 › 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`. 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

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-27943
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105039
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
- https://sourceware.org/bugzilla/show_bug.cgi?id=28995
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/

More about this vulnerability

## Improper Input Validation

low severity

- Manifest file: quay.io/argoproj/argocd:v2.10.16/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:22.04
- Vulnerable module: coreutils
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.10.16 and coreutils@8.32-4.1ubuntu1.2

### Detailed paths

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

## NVD Description

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

- 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