← Übersicht Istio, Red Hat Enterprise Linux

Unauthenticated control plane denial of service attack in Istio

CVE-2022-24726

Hoch · CVSS 7.5 Red Hat: Important Netzwerk · ohne Login Fix verfügbar

Veröffentlicht
09.03.2022
Zuletzt geändert
23.04.2025
EPSS (30 Tage)
1.6 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

Istio is an open platform to connect, manage, and secure microservices. In affected versions the Istio control plane, istiod, is vulnerable to a request processing error, allowing a malicious attacker that sends a specially crafted message which results in the control plane crashing when the validating webhook for a cluster is exposed publicly. This endpoint is served over TLS port 15017, but does not require any authentication from the attacker. For simple installations, Istiod is typically only reachable from within the cluster, limiting the blast radius. However, for some deployments, especially [external istiod](https://istio.io/latest/docs/setup/install/external-controlplane/) topologies, this port is exposed over the public internet. This issue has been patched in versions 1.13.2, 1.12.5 and 1.11.8. Users are advised to upgrade. Users unable to upgrade should disable access to a validating webhook that is exposed to the public internet or restrict the set of IP addresses that can query it to a set of known, trusted entities.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 2 betroffen, 2 behoben, 2 nicht betroffen.

OpenShift Service Mesh 2.0 BetroffenFix ausstehend servicemesh-prometheus
OpenShift Service Mesh 2.1 BetroffenFix ausstehend servicemesh-prometheus
OpenShift Service Mesh 2.0 Behoben servicemesh-2.0.9-3.el8 RHSA-2022:1276
OpenShift Service Mesh 2.1 Behoben servicemesh-2.1.2-4.el8 RHSA-2022:1275
Nicht betroffen (2)
OpenShift Service Mesh 2.0Nicht betroffenverwundbarer Code nicht enthaltenkiali, servicemesh-cni, servicemesh-operator, servicemesh-prometheus, servicemesh-proxy
OpenShift Service Mesh 2.1Nicht betroffenverwundbarer Code nicht enthaltenservicemesh-operator, servicemesh-prometheus, servicemesh-proxy, servicemesh-ratelimit

Betroffene Pakete im beobachteten Stack

CVEistio/istiokein Fix bekanntCVE-2022-24726
NVDistio:istio1.11.8, 1.12.0 → 1.12.5, 1.13.0 → 1.13.2CVE-2022-24726
Red Hat:service_mesh:2.0servicemesh-prometheuskein Fix bekanntCVE-2022-24726
Red Hat:service_mesh:2.0::el8kiali0:v1.24.7.redhat1-1.el8RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.0::el8servicemesh0:2.0.9-3.el8CVE-2022-24726
Red Hat:service_mesh:2.0::el8servicemesh0:2.0.9-3.el8RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.0::el8servicemesh-istioctl0:2.0.9-3.el8RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.0::el8servicemesh-mixc0:2.0.9-3.el8RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.0::el8servicemesh-mixs0:2.0.9-3.el8RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.0::el8servicemesh-pilot-agent0:2.0.9-3.el8RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.0::el8servicemesh-pilot-discovery0:2.0.9-3.el8RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.0::el8servicemesh-prometheus0:2.14.0-16.el8.1RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.0::el8servicemesh-proxy0:2.0.9-3.el8RHSA-2022:1276 (über RHSA-2022:1276)
Red Hat:service_mesh:2.1servicemesh-prometheuskein Fix bekanntCVE-2022-24726
Red Hat:service_mesh:2.1::el8servicemesh0:2.1.2-4.el8CVE-2022-24726
Red Hat:service_mesh:2.1::el8servicemesh0:2.1.2-4.el8RHSA-2022:1275 (über RHSA-2022:1275)
Red Hat:service_mesh:2.1::el8servicemesh-cni0:2.1.2-4.el8RHSA-2022:1275 (über RHSA-2022:1275)
Red Hat:service_mesh:2.1::el8servicemesh-pilot-agent0:2.1.2-4.el8RHSA-2022:1275 (über RHSA-2022:1275)
Red Hat:service_mesh:2.1::el8servicemesh-pilot-discovery0:2.1.2-4.el8RHSA-2022:1275 (über RHSA-2022:1275)
Red Hat:service_mesh:2.1::el8servicemesh-proxy0:2.1.2-4.el8RHSA-2022:1275 (über RHSA-2022:1275)
Red Hat:service_mesh:2.1::el8servicemesh-proxy-debuginfo0:2.1.2-4.el8RHSA-2022:1275 (über RHSA-2022:1275)
Red Hat:service_mesh:2.1::el8servicemesh-proxy-debugsource0:2.1.2-4.el8RHSA-2022:1275 (über RHSA-2022:1275)
Red Hat:service_mesh:2.1::el8servicemesh-proxy-wasm0:2.1.2-4.el8RHSA-2022:1275 (über RHSA-2022:1275)

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 (Netzwerk · ohne Login) 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.