p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in org.apache.spark:spark-parent_2.12

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für org.apache.spark:spark-parent_2.12: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 2

  1. CVE-2023-32007

    Hoch · CVSS 8.8EPSS 75,95%Korrektur verfügbar

    Apache Spark: Shell command injection via Spark UI

    ** UNSUPPORTED WHEN ASSIGNED ** The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as. This

    • Auf 3.2.2 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2022-33891

    Hoch · CVSS 8.8EPSS 93,24%Im KEV-KatalogÖffentlicher ExploitKorrektur verfügbar

    Apache Spark shell command injection vulnerability via Spark UI

    The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as. This affects Apache Spark versions 3.

    • Auf 3.2.2 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →