# Snyk test report

December 15th 2024, 12:26:45 am (UTC+00:00)

Scanned the following paths:

- /argo-cd/argoproj/argo-cd/v2/go.mod (gomodules)
- /argo-cd/ui/yarn.lock (yarn)

12 known vulnerabilities
54 vulnerable dependency paths
2061 dependencies

## Incorrect Implementation of Authentication Algorithm

critical severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 and golang.org/x/crypto/ssh@0.23.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › code.gitea.io/sdk/gitea@0.18.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › golang.org/x/crypto/ssh/knownhosts@0.23.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › code.gitea.io/sdk/gitea@0.18.0 › github.com/go-fed/httpsig@1.1.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/skeema/knownhosts@1.2.2 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › code.gitea.io/sdk/gitea@0.18.0 › golang.org/x/crypto/ssh/agent@0.23.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/xanzy/ssh-agent@0.3.3 › golang.org/x/crypto/ssh/agent@0.23.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/skeema/knownhosts@1.2.2 › golang.org/x/crypto/ssh/knownhosts@0.23.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/skeema/knownhosts@1.2.2 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/xanzy/ssh-agent@0.3.3 › golang.org/x/crypto/ssh/agent@0.23.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/skeema/knownhosts@1.2.2 › golang.org/x/crypto/ssh/knownhosts@0.23.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/skeema/knownhosts@1.2.2 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/xanzy/ssh-agent@0.3.3 › golang.org/x/crypto/ssh/agent@0.23.0 › golang.org/x/crypto/ssh@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.12.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.12.0 › github.com/skeema/knownhosts@1.2.2 › golang.org/x/crypto/ssh/knownhosts@0.23.0 › golang.org/x/crypto/ssh@0.23.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

## LGPL-3.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Module: gopkg.in/retry.v1
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0, github.com/Azure/kubelogin/pkg/token@0.0.20 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/Azure/kubelogin/pkg/token@0.0.20 › gopkg.in/retry.v1@1.0.3

LGPL-3.0 license

More about this vulnerability

## Denial of Service (DoS)

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Vulnerable module: github.com/rs/cors
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0, github.com/improbable-eng/grpc-web/go/grpcweb@0.15.0 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/improbable-eng/grpc-web/go/grpcweb@0.15.0 › github.com/rs/cors@1.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

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Module: github.com/r3labs/diff
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 and github.com/r3labs/diff@1.1.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/r3labs/diff@1.1.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Module: github.com/hashicorp/go-version
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0, code.gitea.io/sdk/gitea@0.18.0 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › code.gitea.io/sdk/gitea@0.18.0 › github.com/hashicorp/go-version@1.6.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Module: github.com/hashicorp/go-retryablehttp
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 and github.com/hashicorp/go-retryablehttp@0.7.7

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/xanzy/go-gitlab@0.91.1 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/cmd@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/api@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/controller@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/cmd@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/api@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/controller@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Module: github.com/hashicorp/go-cleanhttp
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0, github.com/hashicorp/go-retryablehttp@0.7.7 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/hashicorp/go-retryablehttp@0.7.7 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/xanzy/go-gitlab@0.91.1 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/xanzy/go-gitlab@0.91.1 › github.com/hashicorp/go-retryablehttp@0.7.7 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/cmd@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/api@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/controller@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.0.5 › github.com/hashicorp/go-retryablehttp@0.7.7 › github.com/hashicorp/go-cleanhttp@0.5.2

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Module: github.com/gosimple/slug
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 and github.com/gosimple/slug@1.13.1

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/gosimple/slug@1.13.1

MPL-2.0 license

More about this vulnerability

## Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Vulnerable module: github.com/Azure/azure-sdk-for-go/sdk/azidentity
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0, github.com/Azure/kubelogin/pkg/token@0.0.20 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/Azure/kubelogin/pkg/token@0.0.20 › github.com/Azure/azure-sdk-for-go/sdk/azidentity@1.1.0

## Overview

github.com/Azure/azure-sdk-for-go/sdk/azidentity is a module that provides Microsoft Entra ID (formerly Azure Active Directory) token authentication support across the Azure SDK. It includes a set of TokenCredential implementations, which can be used with Azure SDK clients supporting token authentication.

Affected versions of this package are vulnerable to Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in the authentication process. An attacker can elevate privileges by exploiting race conditions during the token validation steps. This is only exploitable if the application is configured to use multiple threads or processes for handling authentication requests.

Notes:

1. An attacker who successfully exploited the vulnerability could elevate privileges and read any file on the file system with SYSTEM access permissions;

2. An attacker who successfully exploits this vulnerability can only obtain read access to the system files by exploiting this vulnerability. The attacker cannot perform write or delete operations on the files;

3. The vulnerability exists in the following credential types: `DefaultAzureCredential` and `ManagedIdentityCredential`;

4. The vulnerability exists in the following credential types:

`ManagedIdentityApplication` (.NET)

`ManagedIdentityApplication` (Java)

`ManagedIdentityApplication` (Node.js)

## Remediation

Upgrade `github.com/Azure/azure-sdk-for-go/sdk/azidentity` to version 1.6.0 or higher.

## References

- GitHub Commit
- GitHub Commit
- GitHub Commit
- GitHub Commit
- GitHub Commit
- GitHub Commit
- GitHub Commit
- Microsoft Advisory

More about this vulnerability

## Regular Expression Denial of Service (ReDoS)

medium severity

- Manifest file: /argo-cd › ui/yarn.lock
- Package Manager: npm
- Vulnerable module: foundation-sites
- Introduced through: argo-cd-ui@1.0.0 and foundation-sites@6.8.1

### Detailed paths

- Introduced through: argo-cd-ui@1.0.0 › foundation-sites@6.8.1
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › foundation-sites@6.8.1

## Overview

foundation-sites is a responsive front-end framework

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to inefficient backtracking in the regular expressions used in URL forms.

## PoC

    https://www.''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

## Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

    regex = /A(B|C+)+D/

This regular expression accomplishes the following:

- `A` The string must start with the letter 'A'
- `(B|C+)+` The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the `+` matches one or more times). The `+` at the end of this section states that we can look for one or more matches of this section.
- `D` Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as `ABBD`, `ABCCCCD`, `ABCBCCCD` and `ACCCCCD`

It most cases, it doesn't take very long for a regex engine to find a match:

    $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
            0.04s user 0.01s system 95% cpu 0.052 total

            $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
            1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

1. CCC
2. CC+C
3. C+CC
4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String | Number of C's | Number of steps
--- | --- | ---
ACCCX | 3 | 38
ACCCCX | 4 | 71
ACCCCCX | 5 | 136
ACCCCCCCCCCCCCCX | 14 | 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

## Remediation

There is no fixed version for `foundation-sites`.

## References

- GitHub Advisory
- GitHub Issue
- Vulnerable Code

More about this vulnerability

## Insufficient Documentation of Error Handling Techniques

low severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Vulnerable module: github.com/golang-jwt/jwt/v4
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 and github.com/golang-jwt/jwt/v4@4.5.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/golang-jwt/jwt/v4@4.5.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/bradleyfalzon/ghinstallation/v2@2.6.0 › github.com/golang-jwt/jwt/v4@4.5.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/bradleyfalzon/ghinstallation/v2@2.6.0 › github.com/golang-jwt/jwt/v4@4.5.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/bradleyfalzon/ghinstallation/v2@2.6.0 › github.com/golang-jwt/jwt/v4@4.5.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/cmd@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/bradleyfalzon/ghinstallation/v2@2.6.0 › github.com/golang-jwt/jwt/v4@4.5.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/Azure/kubelogin/pkg/token@0.0.20 › github.com/Azure/go-autorest/autorest/azure@0.11.29 › github.com/Azure/go-autorest/autorest@0.11.29 › github.com/Azure/go-autorest/autorest/adal@0.9.23 › github.com/golang-jwt/jwt/v4@4.5.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/api@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/bradleyfalzon/ghinstallation/v2@2.6.0 › github.com/golang-jwt/jwt/v4@4.5.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/controller@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/subscriptions@#0802cd427621 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › github.com/bradleyfalzon/ghinstallation/v2@2.6.0 › github.com/golang-jwt/jwt/v4@4.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: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Vulnerable module: github.com/golang-jwt/jwt
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0, github.com/Azure/kubelogin/pkg/token@0.0.20 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/Azure/kubelogin/pkg/token@0.0.20 › github.com/AzureAD/microsoft-authentication-library-for-go/apps/confidential@0.5.2 › github.com/AzureAD/microsoft-authentication-library-for-go/apps/internal/oauth/ops/accesstokens@0.5.2 › github.com/golang-jwt/jwt@3.2.2

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