Cross-user code execution via CWD config loading
Published Oct 26, 2022 · Updated Apr 23, 2025
Arbitrary code execution in Project Jupyter's Jupyter Core before 4.11.2 allows local users to run code as another user. JupyterApp.config_file_paths inserted the process current working directory ahead of trusted configuration directories, causing initialization to load and execute a matching attacker-written Python configuration file. Exploitation requires a different user to start a Jupyter application from an attacker-writable directory; the code runs under that process's account.
Summary
What happened
Arbitrary code execution in Project Jupyter's Jupyter Core before 4.11.2 allows local users to run code as another user. JupyterApp.config_file_paths inserted the process current working directory ahead of trusted configuration directories, causing initialization to load and execute a matching attacker-written Python configuration file. Exploitation requires a different user to start a Jupyter application from an attacker-writable directory; the code runs under that process's account.
The record
- CVE
- CVE-2022-39286
- Published
- Oct 26, 2022
- Updated
- Apr 23, 2025
- Vendor
- Project Jupyter
- Product
- Jupyter Core
- Classifications
- CWE-427, CWE-250, CWE-269, T1574.008
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 4.11.2
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