# Snyk test report

December 15th 2024, 12:24:50 am (UTC+00:00)

Scanned the following paths:

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

23 known vulnerabilities
103 vulnerable dependency paths
2354 dependencies

## Incorrect Implementation of Authentication Algorithm

critical severity

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

### Detailed paths

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

## Overview

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

Affected versions of this package are vulnerable to Incorrect Implementation of Authentication Algorithm when the key passed in the last call before a connection is established is assumed to be the key used for authentication. It is not necessarily the authentication key in use, and this allows attackers who can control the key cache by making their own carefully-timed connections to bypass authorization with subsequent legitimate `ServerConfig.PublicKeyCallback` callbacks.

Note: The assumed caching behavior of this callback is not documented and is therefore considered human error, but the project maintainers have observed reliance on it for authorization decisions in production. In fact, the assumption is negated in the documentation, which states "A call to this function does not guarantee that the key offered is in fact used to authenticate." The behavior after upgrading still allows the possibility of an attacker forcing their own key to be the one in the cache when the callback is invoked if the client is using a different authentication method such as `PasswordCallback`, `KeyboardInteractiveCallback`, or `NoClientAuth`. It is therefore recommended to rely on the return values of the connection itself, found in `ServerConn.Permissions` for further authorization steps.

## Remediation

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

## References

- GitHub Commit
- GitHub Issue
- go.dev Commit
- go.dev Issue
- Google Groups Forum
- Go Vulnerability Database

More about this vulnerability

## Insecure Storage of Sensitive Information

medium severity

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

### Detailed paths

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

## NVD Description

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

A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-10041
- https://access.redhat.com/security/cve/CVE-2024-10041
- https://bugzilla.redhat.com/show_bug.cgi?id=2319212
- https://access.redhat.com/errata/RHSA-2024:9941
- https://access.redhat.com/errata/RHSA-2024:10379

More about this vulnerability

## Improper Authentication

medium severity

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

### Detailed paths

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

## NVD Description

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

A flaw was found in pam_access, where certain rules in its configuration file are mistakenly treated as hostnames. This vulnerability allows attackers to trick the system by pretending to be a trusted hostname, gaining unauthorized access. This issue poses a risk for systems that rely on this feature to control who can access certain services or terminals.

## Remediation

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

## References

- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-10963
- https://access.redhat.com/security/cve/CVE-2024-10963
- https://bugzilla.redhat.com/show_bug.cgi?id=2324291

More about this vulnerability

## CVE-2024-26462

medium severity

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

### Detailed paths

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

## NVD Description

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

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: quay.io/argoproj/argocd:v2.13.2/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:v2.13.2/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:v2.13.2/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.14.0

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## Release of Invalid Pointer or Reference

low severity

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

### Detailed paths

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

### Detailed paths

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

## NVD Description

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

A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.

## Remediation

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

## References

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

More about this vulnerability

## CVE-2024-41996

low severity

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

### Detailed paths

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

## NVD Description

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

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

## Remediation

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

## References

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

More about this vulnerability

## Information Exposure

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/dirmngr@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/gpg@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/gpg-agent@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › apt@2.7.14build2 › apt/libapt-pkg6.0t64@2.7.14build2 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › apt@2.7.14build2 › gnupg2/gpgv@2.4.4-2ubuntu17 › libgcrypt20@1.10.3-2build1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › 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@v2.13.2 › apt@2.7.14build2 › adduser@3.137ubuntu1 › shadow/passwd@1:4.13+dfsg1-4ubuntu3.2 › pam/libpam-modules@1.5.3-5ubuntu5.1 › systemd/libsystemd0@255.4-1ubuntu8.4 › libgcrypt20@1.10.3-2build1

## NVD Description

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

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

## Remediation

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

## References

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

More about this vulnerability

## CVE-2024-26458

low severity

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

### Detailed paths

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

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `krb5` package and not the `krb5` package as distributed by `Ubuntu`. See `How to fix?` for `Ubuntu: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:v2.13.2/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:24.04
- Vulnerable module: krb5/libk5crypto3
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2, git@1:2.43.0-1ubuntu7.1 and others

### Detailed paths

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

## NVD Description

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/gpgv@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › apt@2.7.14build2 › gnupg2/gpgv@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/dirmngr@2.4.4-2ubuntu17 › gnupg2/gpgconf@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/gpg-agent@2.4.4-2ubuntu17 › gnupg2/gpgconf@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/gpg@2.4.4-2ubuntu17 › gnupg2/gpgconf@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/dirmngr@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › gnupg2/gpg@2.4.4-2ubuntu17
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › 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:v2.13.2/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:24.04
- Vulnerable module: glibc/libc-bin
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 and glibc/libc-bin@2.39-0ubuntu8.3

### Detailed paths

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

## NVD Description

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

sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.

## Remediation

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

## References

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

More about this vulnerability

## Insufficient Documentation of Error Handling Techniques

low severity

- Manifest file: quay.io/argoproj/argocd:v2.13.2/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: github.com/golang-jwt/jwt/v4
- Introduced through: github.com/argoproj/argo-cd/v2@* and github.com/golang-jwt/jwt/v4@v4.5.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › github.com/golang-jwt/jwt/v4@v4.5.0

## Overview

Affected versions of this package are vulnerable to Insufficient Documentation of Error Handling Techniques in the `ParseWithClaims` function. An attacker can exploit this to accept invalid tokens by only checking for specific errors and ignoring others.

## Workaround

Users who are not able to upgrade to the fixed version should make sure that they are properly checking for all errors, see `example_test.go`

## Remediation

Upgrade `github.com/golang-jwt/jwt/v4` to version 4.5.1 or higher.

## References

- GitHub Commit

More about this vulnerability

## Insufficient Documentation of Error Handling Techniques

low severity

- Manifest file: quay.io/argoproj/argocd:v2.13.2/argoproj/argo-cd/v2 › /usr/local/bin/argocd
- Package Manager: golang
- Vulnerable module: github.com/golang-jwt/jwt
- Introduced through: github.com/argoproj/argo-cd/v2@* and github.com/golang-jwt/jwt@v3.2.2+incompatible

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@* › github.com/golang-jwt/jwt@v3.2.2+incompatible

## Overview

Affected versions of this package are vulnerable to Insufficient Documentation of Error Handling Techniques in the `ParseWithClaims` function. An attacker can exploit this to accept invalid tokens by only checking for specific errors and ignoring others.

## Workaround

Users who are not able to upgrade to the fixed version should make sure that they are properly checking for all errors, see `example_test.go`

## Remediation

A fix was pushed into the `master` branch but not yet published.

## References

- GitHub Commit

More about this vulnerability

## Improper Input Validation

low severity

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

### Detailed paths

- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › git@1:2.43.0-1ubuntu7.1 › git/git-man@1:2.43.0-1ubuntu7.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › git@1:2.43.0-1ubuntu7.1
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 › git-lfs@3.4.1-1ubuntu0.2 › 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:v2.13.2/argoproj/argocd › Dockerfile
- Package Manager: ubuntu:24.04
- Vulnerable module: coreutils
- Introduced through: docker-image|quay.io/argoproj/argocd@v2.13.2 and coreutils@9.4-3ubuntu6

### Detailed paths

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