- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202301-04
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: High
    Title: jupyter_core: Arbitrary Code Execution
     Date: January 11, 2023
     Bugs: #878497
       ID: 202301-04

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
A vulnerability has been discovered in jupyter_core which could allow
for the execution of code as another user.

Background
=========
jupyter_core contains core Jupyter functionality.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-python/jupyter_core    < 4.11.2                    >= 4.11.2

Description
==========
jupyter_core trusts files for execution in the current working directory
without validating ownership of those files.

Impact
=====
By writing to a directory that is used a the current working directory
for jupyter_core by another user, users can elevate privileges to those
of another user.

Workaround
=========
There is no known workaround at this time.

Resolution
=========
All jupyter_core users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-python/jupyter_core-4.11.2"

References
=========
[ 1 ] CVE-2022-39286
      https://nvd.nist.gov/vuln/detail/CVE-2022-39286

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202301-04

Concerns?
========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
======
Copyright 2023 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-202301-04: jupyter_core: Arbitrary Code Execution

A vulnerability has been discovered in jupyter_core which could allow for the execution of code as another user.

Summary

jupyter_core trusts files for execution in the current working directory without validating ownership of those files.

Resolution

All jupyter_core users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-python/jupyter_core-4.11.2"

References

[ 1 ] CVE-2022-39286 https://nvd.nist.gov/vuln/detail/CVE-2022-39286

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202301-04

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: High
Title: jupyter_core: Arbitrary Code Execution
Date: January 11, 2023
Bugs: #878497
ID: 202301-04

Synopsis

A vulnerability has been discovered in jupyter_core which could allow for the execution of code as another user.

Background

jupyter_core contains core Jupyter functionality.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-python/jupyter_core < 4.11.2 >= 4.11.2

Impact

===== By writing to a directory that is used a the current working directory for jupyter_core by another user, users can elevate privileges to those of another user.

Workaround

There is no known workaround at this time.

Related News