Live › vulnerability › CVE-2022-33891
Go to dashboardApache Spark has a command injection flaw in its Spark UI when Access Control Lists are enabled. An attacker who can reach the UI can get commands run on the host running Spark.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply updates per vendor instructions.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Apache Spark | vendor | – | – |
| apache spark | vendor | <= 3.0.3 | – |
| apache spark | vendor | >= 3.1.1, <= 3.1.2 | – |
| apache spark | vendor | >= 3.2.0, <= 3.2.1 | – |
Unknown from the sources.
Apply the vendor update per Apache Spark instructions; the fixed version is not stated in the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.0.3 and earlier, versions 3.1.1 to 3.1.2, and versions 3.2.0 to 3.2.1.
This page as .md · .json · in your agent: get_signal("CVE-2022-33891")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.