CVE-2023-32007

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 issue was disclosed earlier as CVE-2022-33891, but incorrectly claimed version 3.1.3 (which has since gone EOL) would not be affected.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Users are recommended to upgrade to a supported version of Apache Spark, such as version 3.4.0.

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2023-32007 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2023-32007? CVE-2023-32007 is a high-severity command injection vulnerability in org.apache.spark:spark-parent_2.12 (maven), affecting versions >= 3.1.1, < 3.2.2. It is fixed in 3.2.2. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
2. How severe is CVE-2023-32007? CVE-2023-32007 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2023-32007?
   • org.apache.spark:spark-parent_2.12 (maven) (versions >= 3.1.1, < 3.2.2)
   • pyspark (pip) (versions >= 3.1.1, < 3.2.2)
4. Is there a fix for CVE-2023-32007? Yes. CVE-2023-32007 is fixed in 3.2.2. Upgrade to this version or later.
5. Is CVE-2023-32007 exploitable, and should I be worried? Whether CVE-2023-32007 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-32007 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-32007?
   • Upgrade org.apache.spark:spark-parent_2.12 to 3.2.2 or later
   • Upgrade pyspark to 3.2.2 or later

Other vulnerabilities in org.apache.spark:spark-parent_2.12