Privilege escalation via proxy-user custom classpath
Published Apr 17, 2023 · Updated Oct 21, 2024
Improper privilege management in Apache Spark before 3.4.0 allows remote authenticated users to execute code as the submitting user. SparkSubmit retained attacker-supplied child-classpath entries in proxy-user cluster mode and loaded their classes into its submission class loader. Architectures that use proxy-user isolation, including Apache Livy deployments, expose the submitter's privileges rather than the restricted proxy identity.
Summary
What happened
Improper privilege management in Apache Spark before 3.4.0 allows remote authenticated users to execute code as the submitting user. SparkSubmit retained attacker-supplied child-classpath entries in proxy-user cluster mode and loaded their classes into its submission class loader. Architectures that use proxy-user isolation, including Apache Livy deployments, expose the submitter's privileges rather than the restricted proxy identity.
The record
- CVE
- CVE-2023-22946
- Published
- Apr 17, 2023
- Updated
- Oct 21, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Spark
- Classifications
- CWE-269, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 2023CVE publishedPublication date reported by the CVE source.
- Oct 21, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo