CVE-2023-22946

In Apache Spark versions prior to versions 3.4.0 and 3.3.3, applications using spark-submit can specify a proxy-user to run as, limiting privileges. The application can execute code with the privileges of the submitting user, however, by providing malicious configuration-related classes on the classpath. This affects architectures relying on proxy-user, for example those using Apache Livy to manage submitted applications.

Update to Apache Spark 3.4.0, 3.3.3, or later, and ensure that spark.submit.proxyUser.allowCustomClasspathInClusterMode is set to its default of "false", and is not overridden by submitted applications.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2023-22946 has a CVSS score of 9.9 (Critical). 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.3.3, 3.3.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2023-22946? CVE-2023-22946 is a critical-severity improper privilege management vulnerability in org.apache.spark:spark-core_2.12 (maven), affecting versions <= 3.3.2. It is fixed in 3.3.3, 3.3.2. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is CVE-2023-22946? CVE-2023-22946 has a CVSS score of 9.9 (Critical). 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-22946?
   • org.apache.spark:spark-core_2.12 (maven) (versions <= 3.3.2)
   • org.apache.spark:spark-core_2.13 (maven) (versions <= 3.3.2)
   • pyspark (pip) (versions < 3.3.2)
4. Is there a fix for CVE-2023-22946? Yes. CVE-2023-22946 is fixed in 3.3.3, 3.3.2. Upgrade to this version or later.
5. Is CVE-2023-22946 exploitable, and should I be worried? Whether CVE-2023-22946 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-22946 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-22946?
   • Upgrade org.apache.spark:spark-core_2.12 to 3.3.3 or later
   • Upgrade org.apache.spark:spark-core_2.13 to 3.3.3 or later
   • Upgrade pyspark to 3.3.2 or later