← Übersicht Argo CD

Unauthenticated pprof endpoints on the controller and API server metrics ports

GHSA-9mrf-wvv5-62p9

Mittel · CVSS 5.4 Nachbarnetz Fix verfügbar

Veröffentlicht
20.11.2026 04:38
Zuletzt geändert
20.11.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### Impact The application controller and the API server served Go's `pprof` profiling endpoints (`/debug/pprof/`) on their metrics ports, always on and with no authentication. Anyone who could reach those ports could download CPU and heap profiles and other runtime details, which can contain sensitive data, and could trigger profiling that uses extra resources on the component. All versions from v2.2.0 onward are affected, up to the patched version below. The endpoints were added in [49b71522c](https://github.com/argoproj/argo-cd/commit/49b71522c447da73d9e395de2aabd8d4c5176c3e) ([#7533](https://github.com/argoproj/argo-cd/pull/7533)). The metrics ports are usually not exposed through an Ingress, so an attacker typically needs network access from inside the cluster. ### Patches A patch for this vulnerability has been released in the following Argo CD version: * v2.13.0 Since v2.13.0 the profiling endpoints are off by default and return 401 unless explicitly enabled with `controller.profile.enabled`, `server.profile.enabled`, `reposerver.profile.enabled` or `applicationsetcontroller.profile.enabled` in [`argocd-cmd-params-cm`](https://argo-cd.readthedocs.io/en/stable/operator-manual/argocd-cmd-params-cm-yaml/). ### Workarounds Restrict network access to the application controller and API server [metrics](https://argo-cd.readthedocs.io/en/stable/operator-manual/metrics/) ports, for example with Kubernetes NetworkPolicies, so that only your monitoring system can reach them. ### Credits The Argo CD team would like to thank @agilgur5 for responsibly disclosing this issue. ### References * Fix: [26fb098ae](https://github.com/argoproj/argo-cd/commit/26fb098ae85e00dd453eabd010c557f2b34fec3a) ([#19327](https://github.com/argoproj/argo-cd/pull/19327)) * Introducing commit: [49b71522c](https://github.com/argoproj/argo-cd/commit/49b71522c447da73d9e395de2aabd8d4c5176c3e) ([#7533](https://github.com/argoproj/argo-cd/pull/7533)), first released in v2.2.0 * [Your pprof is showing](https://mmcloughlin.com/posts/your-pprof-is-showing) ### For more information * Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions) * Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd

Betroffene Pakete im beobachteten Stack

Gogithub.com/argoproj/argo-cd/v22.2.0 → 2.13.0GHSA-9mrf-wvv5-62p9

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Nachbarnetz) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.