Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
CISA KEV·Added 2023-03-07 — agencies required to remediate by 2023-03-28
Maven🐍 PyPI

GHSA-4x9r-j582-cgr8

HIGH

Apache Spark UI can allow impersonation if ACLs enabled

Also known asBIT-spark-2022-33891CVE-2022-33891PYSEC-2022-236
Published
Jul 19, 2022
Updated
Jun 9, 2026
Affected
4 pkgs
Patched
3 / 4
Exploits
13 known

EPSS Exploitation Probability

via FIRST.org ↗
93.0%probability of exploitation in next 30 days
Very High Risk100th percentile0.00%
92.5%93.0%93.6%94.1%93.6%93.0%Jan 26May 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected
org.apache.spark:spark-parent_2.12org.apache.spark:spark-parent_2.12🐍pyspark🐍pyspark

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

A previous version of this advisory incorrectly stated that version 3.1.3 was not vulnerable. Per GHSA-59hw-j9g6-mfg3, version 3.1.3 is vulnerable and vulnerable version ranges in this advisory have been changed to reflect the correct information.

Affected Packages

4 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.spark:spark-parent_2.12all versionsNo fix
Mavenorg.apache.spark:spark-parent_2.123.1.1&&< 3.2.23.2.2
🐍PyPIpysparkall versions3.1.3
🐍PyPIpyspark3.2.0&&< 3.2.23.2.2
Exploits & PoCs
13

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.spark:spark-parent_2.12. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    No patched version of org.apache.spark:spark-parent_2.12 has shipped for GHSA-4x9r-j582-cgr8 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-4x9r-j582-cgr8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4x9r-j582-cgr8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 current
O3 Security · Impact-Aware SCA

Is GHSA-4x9r-j582-cgr8 in your dependencies?

O3 detects GHSA-4x9r-j582-cgr8 across Maven, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.