# Snyk test report
19 known vulnerabilities found in 154 vulnerable dependency paths.

June 15th 2025, 12:31:33 am (UTC+00:00)

Scanned the following paths:

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

19 known vulnerabilities
154 vulnerable dependency paths
2149 dependencies

## Allocation of Resources Without Limits or Throttling

high severity

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

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jws@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jwt@0.23.0 › golang.org/x/oauth2/jws@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jws@0.23.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 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jws@0.23.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 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jws@0.23.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#0802cd427621 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jwt@0.23.0 › golang.org/x/oauth2/jws@0.23.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 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jws@0.23.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 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jws@0.23.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 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jwt@0.23.0 › golang.org/x/oauth2/jws@0.23.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 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jwt@0.23.0 › golang.org/x/oauth2/jws@0.23.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 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jwt@0.23.0 › golang.org/x/oauth2/jws@0.23.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 › google.golang.org/api/chat/v1@0.132.0 › google.golang.org/api/transport/http@0.132.0 › google.golang.org/api/option@0.132.0 › google.golang.org/api/internal@0.132.0 › golang.org/x/oauth2/google@0.23.0 › golang.org/x/oauth2/jwt@0.23.0 › golang.org/x/oauth2/jws@0.23.0

## Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to improper parsing of malformed tokens which can lead to memory consumption.

## Remediation

Upgrade `golang.org/x/oauth2/jws` to version 0.27.0 or higher.

## References

- GitHub Commit
- GitHub Commit
- GitHub Issue
- GitHub PR
- Go Advisory

More about this vulnerability

## Server-side Request Forgery (SSRF)

high severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Vulnerable module: golang.org/x/net/http/httpproxy
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 and golang.org/x/net/http/httpproxy@0.33.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › golang.org/x/net/http/httpproxy@0.33.0

## Overview

golang.org/x/net/http/httpproxy is a package for HTTP proxy determination based on environment variables, as provided by net/http's ProxyFromEnvironment function

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in `proxy.go`, because hostname matching against proxy patterns may treat an IPv6 zone ID as a hostname component. An environment variable value like `*.example.com` could be matched to a request intended for `[::1%25.example.com]:80`.

## Remediation

Upgrade `golang.org/x/net/http/httpproxy` to version 0.36.0 or higher.

## References

- Git Commit
- GitHub Commit
- GitHub Commit
- GitHub Issue

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

high 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.32.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › code.gitea.io/sdk/gitea@0.19.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › golang.org/x/crypto/ssh/knownhosts@0.32.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › code.gitea.io/sdk/gitea@0.19.0 › github.com/go-fed/httpsig@1.1.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/skeema/knownhosts@1.3.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › code.gitea.io/sdk/gitea@0.19.0 › golang.org/x/crypto/ssh/agent@0.32.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/xanzy/ssh-agent@0.3.3 › golang.org/x/crypto/ssh/agent@0.32.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/skeema/knownhosts@1.3.0 › golang.org/x/crypto/ssh/knownhosts@0.32.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/skeema/knownhosts@1.3.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/client@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/xanzy/ssh-agent@0.3.3 › golang.org/x/crypto/ssh/agent@0.32.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5/plumbing/transport/client@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/skeema/knownhosts@1.3.0 › golang.org/x/crypto/ssh/knownhosts@0.32.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/client@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/skeema/knownhosts@1.3.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/client@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/xanzy/ssh-agent@0.3.3 › golang.org/x/crypto/ssh/agent@0.32.0 › golang.org/x/crypto/ssh@0.32.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-git/go-git/v5@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/client@5.13.1 › github.com/go-git/go-git/v5/plumbing/transport/ssh@5.13.1 › github.com/skeema/knownhosts@1.3.0 › golang.org/x/crypto/ssh/knownhosts@0.32.0 › golang.org/x/crypto/ssh@0.32.0

## Overview

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

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in `handshakeTransport` in `handshake.go`. An internal queue gets populated with received packets during the key exchange process, while waiting for the client to send a `SSH_MSG_KEXINIT`. An attacker can cause the server to become unresponsive to new connections by delaying or withholding this message, or by causing the queue to consume all available memory.

## Remediation

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

## References

- Git Commit
- Go Issue
- Vulnerability Advisory

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

## Improper Validation of Syntactic Correctness of Input

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v2 › go.mod
- Package Manager: golang
- Vulnerable module: golang.org/x/net/html
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0, k8s.io/client-go/tools/portforward@0.31.0 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › k8s.io/client-go/tools/portforward@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/diff@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/sync@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/utils/kube@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/cache@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/utils/kube@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/health@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/utils/kube@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/sync/common@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/utils/kube@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/sync/hook@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/sync/hook/helm@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/sync/common@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/utils/kube@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/sync/syncwaves@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/sync/hook/helm@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/sync/common@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/utils/kube@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/argoproj/gitops-engine/pkg/sync/ignore@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/sync/hook@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/sync/hook/helm@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/sync/common@#4c6e03c46314 › github.com/argoproj/gitops-engine/pkg/utils/kube@#4c6e03c46314 › k8s.io/kubectl/pkg/cmd/util@0.31.0 › k8s.io/kubectl/pkg/util/templates@0.31.0 › k8s.io/kubectl/pkg/util/term@0.31.0 › k8s.io/client-go/tools/remotecommand@0.31.0 › k8s.io/client-go/transport/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/httpstream/spdy@0.31.0 › k8s.io/apimachinery/pkg/util/proxy@0.31.0 › golang.org/x/net/html@0.33.0

## Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Improper Validation of Syntactic Correctness of Input in the tokenizer in `token.go`, which incorrectly interprets tags as closing tags, allowing malicious input to be incorrectly processed and the DOM to be corrupted.

## Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, `<` can be coded as `&lt`; and `>` can be coded as `&gt`; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses `<` and `>` as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

### Types of attacks

There are a few methods by which XSS can be manipulated:

Type | Origin | Description
--- | --- | ---
Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated |  | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

### Affected environments

The following environments are susceptible to an XSS attack:

- Web servers
- Application servers
- Web application environments

### How to prevent

This section describes the top best practices designed to specifically protect your code:

- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as `?`, `&`, `/`, `<`, `>` and spaces to their respective HTML or URL encoded equivalents.
- Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

## Remediation

Upgrade `golang.org/x/net/html` to version 0.38.0 or higher.

## References

- GitHub Commit
- GitHub Issue
- Google Groups Announcement

More about this vulnerability

## Unexpected Status Code or Return Value

medium severity

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

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/redis/go-redis/v9@9.7.1
- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-redis/cache/v9@9.0.0 › github.com/redis/go-redis/v9@9.7.1

## Overview

Affected versions of this package are vulnerable to Unexpected Status Code or Return Value in `initConn()`, which causes out of order responses when `CLIENT SETINFO` times out while establishing a connection.

## Workaround

This vulnerability can be avoided by setting `DisableIndentity` to true when initializing a client.

## Remediation

Upgrade `github.com/redis/go-redis/v9` to version 9.5.5, 9.6.3, 9.7.2 or higher.

## References

- GitHub Commit
- 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.19.0 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › code.gitea.io/sdk/gitea@0.19.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.109.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/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.109.0 › 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.109.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/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.14.0

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

medium severity

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

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v2@0.0.0 › github.com/go-jose/go-jose/v3@3.0.3

## Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to the use of `strings.Split` to split JWT tokens. An attacker can cause memory exhaustion and service disruption by sending numerous malformed tokens with a large number of `.` characters.

## Workaround

This vulnerability can be mitigated by pre-validating that payloads passed to Go JOSE do not contain an excessive number of `.` characters.

## Remediation

Upgrade `github.com/go-jose/go-jose/v3` to version 3.0.4 or higher.

## References

- GitHub Commit
- GitHub Release

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

## Regular Expression Denial of Service (ReDoS)

medium severity

- Manifest file: /argo-cd › ui/yarn.lock
- Package Manager: npm
- Vulnerable module: @babel/runtime
- Introduced through: argo-cd-ui@1.0.0, argo-ui@1.0.0 and others

### Detailed paths

- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @ant-design/cssinjs@1.10.1 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @ant-design/icons@5.1.4 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @ant-design/react-slick@1.0.1 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/color-picker@1.2.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-checkbox@3.1.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-collapse@3.7.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-dialog@9.1.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-drawer@6.2.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-image@5.17.1 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-input@1.0.4 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-input-number@7.4.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-mentions@2.3.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-motion@2.7.3 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-notification@5.0.4 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-pagination@3.5.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-picker@3.8.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-progress@3.4.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-rate@2.12.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-resize-observer@1.2.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-segmented@2.2.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-slider@10.1.1 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-table@7.32.1 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-tabs@12.7.1 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-tooltip@6.0.1 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-tree-select@5.9.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-upload@4.3.3 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-cascader@3.12.0 › rc-select@14.5.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-cascader@3.12.0 › rc-tree@5.7.6 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-drawer@6.2.0 › rc-motion@2.6.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-mentions@2.3.0 › rc-menu@9.9.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-mentions@2.3.0 › rc-textarea@1.2.3 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-table@7.32.1 › @rc-component/context@1.3.0 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/tour@1.8.0 › @rc-component/trigger@1.13.6 › rc-align@4.0.11 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/tour@1.8.0 › @rc-component/trigger@1.13.6 › rc-motion@2.4.4 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-cascader@3.12.0 › rc-select@14.5.2 › rc-overflow@1.2.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-mentions@2.3.0 › rc-menu@9.9.2 › rc-overflow@1.3.1 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-cascader@3.12.0 › rc-select@14.5.2 › rc-overflow@1.2.2 › rc-resize-observer@1.1.2 › @babel/runtime@7.16.7
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/mutate-observer@1.0.0 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/tour@1.8.0 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-dropdown@4.1.0 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-field-form@1.32.2 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @ant-design/cssinjs@1.10.1 › rc-util@5.34.0 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/tour@1.8.0 › @rc-component/portal@1.1.1 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/tour@1.8.0 › @rc-component/trigger@1.13.6 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-dialog@9.1.0 › rc-util@5.24.2 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-input-number@7.4.2 › @rc-component/mini-decimal@1.1.0 › @babel/runtime@7.19.0
- Introduced through: argo-cd-ui@1.0.0 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › react-router@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › react-router-dom@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › react-form@2.16.3 › react-redux@5.1.2 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › react-router@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › react-router-dom@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › react-form@2.16.3 › react-redux@5.1.2 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › react-router-dom@4.3.1 › react-router@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › react-router-dom@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › react-form@2.16.3 › react-redux@5.1.2 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-cascader@3.12.0 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › react-router-dom@4.3.1 › react-router@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › react-router-dom@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › react-form@2.16.3 › react-redux@5.1.2 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › react-router-dom@4.3.1 › react-router@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-dropdown@4.1.0 › rc-util@5.20.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › react-router-dom@4.3.1 › react-router@4.3.1 › history@4.10.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/tour@1.8.0 › @rc-component/trigger@1.13.6 › rc-align@4.0.11 › rc-util@5.16.1 › @babel/runtime@7.14.6
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › @rc-component/tour@1.8.0 › @rc-component/trigger@1.13.6 › rc-resize-observer@1.3.1 › @babel/runtime@7.22.5
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-cascader@3.12.0 › rc-select@14.5.2 › rc-virtual-list@3.5.2 › @babel/runtime@7.22.5
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-steps@6.0.0 › @babel/runtime@7.17.2
- Introduced through: argo-cd-ui@1.0.0 › date-fns@2.30.0 › @babel/runtime@7.21.5
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › antd@5.6.2 › rc-switch@4.1.0 › @babel/runtime@7.21.5
- Introduced through: argo-cd-ui@1.0.0 › react-virtualized@9.22.3 › @babel/runtime@7.20.13
- Introduced through: argo-cd-ui@1.0.0 › react-virtualized@9.22.3 › dom-helpers@5.2.1 › @babel/runtime@7.20.13
- Introduced through: argo-cd-ui@1.0.0 › redoc@2.4.0 › polished@4.3.1 › @babel/runtime@7.26.9

## Overview

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in the `replace()` method in `wrapRegExp.js`. An attacker can cause degradation in performance by supplying input strings that exploit the quadratic complexity of the replacement algorithm.

This is only exploitable when all of the following conditions are met:

1. The code passes untrusted strings in the second argument to `.replace()`.

2. The compiled regular expressions being applied contain named capture groups.

In the case of `@babel/preset-env`, if the `targets` option is in use the application will be vulnerable under either of the following conditions:

1. A browser older than Chrome 64, Opera 71, Edge 79, Firefox 78, Safari 11.1, or Node.js 10 is used when processing named capture groups.

2. A browser older than Chrome/Edge 126, Opera 112, Firefox 129, Safari 17.4, or Node.js 23 is used when processing duplicated named capture groups.

Note: The project maintainers advise that "just updating your Babel dependencies is not enough: you will also need to re-compile your code."

## Workaround

This vulnerability can be avoided by filtering out input containing a `$<` that is not followed by a `>`.

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

Upgrade `@babel/runtime` to version 7.26.10, 8.0.0-alpha.17 or higher.

## References

- GitHub Commit
- GitHub Gist
- GitHub PR

More about this vulnerability

## Arbitrary Code Injection

low severity

- Manifest file: /argo-cd › ui/yarn.lock
- Package Manager: npm
- Vulnerable module: prismjs
- Introduced through: argo-cd-ui@1.0.0, redoc@2.4.0 and others

### Detailed paths

- Introduced through: argo-cd-ui@1.0.0 › redoc@2.4.0 › prismjs@1.29.0

## Overview

prismjs is a lightweight, robust, elegant syntax highlighting library.

Affected versions of this package are vulnerable to Arbitrary Code Injection via the `document.currentScript` lookup process. An attacker can manipulate the web page content and execute unintended actions by injecting HTML elements that overshadow legitimate DOM elements.

Note:

This is only exploitable if the application accepts untrusted input containing HTML but not direct JavaScript.

## Remediation

Upgrade `prismjs` to version 1.30.0 or higher.

## References

- GitHub Commit
- GitHub Gist
- GitHub PR
- 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
- 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

## Insecure Randomness

low severity

- Manifest file: /argo-cd › ui/yarn.lock
- Package Manager: npm
- Vulnerable module: formidable
- Introduced through: argo-cd-ui@1.0.0, superagent@8.1.2 and others

### Detailed paths

- Introduced through: argo-cd-ui@1.0.0 › superagent@8.1.2 › formidable@2.1.2

## Overview

Affected versions of this package are vulnerable to Insecure Randomness due to its use of the `hexoid()` function in the generation of fingerprint IDs.

## Remediation

Upgrade `formidable` to version 2.1.3, 3.5.3 or higher.

## References

- GitHub Commit
- Vulnerability Report

More about this vulnerability

## Regular Expression Denial of Service (ReDoS)

low severity

- Manifest file: /argo-cd › ui/yarn.lock
- Package Manager: npm
- Vulnerable module: brace-expansion
- Introduced through: argo-cd-ui@1.0.0, minimatch@3.1.2 and others

### Detailed paths

- Introduced through: argo-cd-ui@1.0.0 › minimatch@3.1.2 › brace-expansion@1.1.11
- Introduced through: argo-cd-ui@1.0.0 › redoc@2.4.0 › @redocly/openapi-core@1.30.0 › minimatch@5.1.6 › brace-expansion@2.0.1

## Overview

brace-expansion is a Brace expansion as known from sh/bash

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in the `expand()` function, which is prone to catastrophic backtracking on very long malicious inputs.

## PoC

    import index from "./index.js";

            let str = "{a}" + ",".repeat(100000) + "\u0000";

            let startTime = performance.now();

            const result = index(str);

            let endTime = performance.now();

            let timeTaken = endTime - startTime;

            console.log(`匹配耗时: ${timeTaken.toFixed(3)} 毫秒`);

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

Upgrade `brace-expansion` to version 1.1.12, 2.0.2, 3.0.1, 4.0.1 or higher.

## References

- GitHub Advisory
- GitHub Commit
- GitHub Gist
- GitHub PR

More about this vulnerability