Bug 2138127 (CVE-2022-39286) - CVE-2022-39286 jupyter-core: arbitrary code execution
Summary: CVE-2022-39286 jupyter-core: arbitrary code execution
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2022-39286
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2138129 2138128
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-27 10:21 UTC by ybuenos
Modified: 2022-12-02 22:21 UTC (History)
0 users

Fixed In Version: python-jupyter-core 4.11.2
Doc Type: ---
Doc Text:
jupyter core before 4.11.2 contains an arbitrary code execution vulnerability resulting from executing untrusted files in the current working directory, which allows one user to run code as another.
Clone Of:
Environment:
Last Closed: 2022-12-02 22:21:17 UTC
Embargoed:


Attachments (Terms of Use)

Description ybuenos 2022-10-27 10:21:56 UTC
Jupyter Core is a package for the core common functionality of Jupyter projects. Jupyter Core prior to version 4.11.2 contains an arbitrary code execution vulnerability in `jupyter_core` that stems from `jupyter_core` executing untrusted files in CWD. This vulnerability allows one user to run code as another. Version 4.11.2 contains a patch for this issue. There are no known workarounds.

https://github.com/jupyter/jupyter_core/commit/1118c8ce01800cb689d51f655f5ccef19516e283
https://github.com/jupyter/jupyter_core/security/advisories/GHSA-m678-f26j-3hrp

Comment 1 ybuenos 2022-10-27 10:22:16 UTC
Created python-jupyter-core tracking bugs for this issue:

Affects: epel-all [bug 2138129]
Affects: fedora-all [bug 2138128]

Comment 2 Product Security DevOps Team 2022-12-02 22:21:15 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.