Skip to content

Execution with Unnecessary Privileges in JupyterApp

High severity GitHub Reviewed Published Oct 26, 2022 in jupyter/jupyter_core • Updated Sep 2, 2023

Package

pip jupyter-core (pip)

Affected versions

< 4.11.2

Patched versions

4.11.2

Description

Impact

What kind of vulnerability is it? Who is impacted?
We’d like to disclose an arbitrary code execution vulnerability in jupyter_core that stems from jupyter_core executing untrusted files in the current working directory. This vulnerability allows one user to run code as another.

Patches

Has the problem been patched? What versions should users upgrade to?
Users should upgrade to jupyter_core>=4.11.2.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?
No

References

Are there any links users can visit to find out more?
Similar advisory in IPython

References

@blink1073 blink1073 published to jupyter/jupyter_core Oct 26, 2022
Published by the National Vulnerability Database Oct 26, 2022
Published to the GitHub Advisory Database Oct 26, 2022
Reviewed Oct 26, 2022
Last updated Sep 2, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.495%
(77th percentile)

Weaknesses

CVE ID

CVE-2022-39286

GHSA ID

GHSA-m678-f26j-3hrp

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.