Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web applications like Jupyter Notebook. Prior to version 1.17.1, if notebook server is started with a value of `root_dir` that contains the starting user's home directory, then the underlying REST API can be used to leak the access token assigned at start time by guessing/brute forcing the PID of the jupyter server. While this requires an authenticated user session, this URL can be used from a cross-site scripting payload or from a hooked or otherwise compromised browser to leak this access token to a malicious third party. This token can be used along with the REST API to interact with Jupyter services/notebooks such as modifying or overwriting critical files, such as .bashrc or .ssh/authorized_keys, allowing a malicious user to read potentially sensitive data and possibly gain control of the impacted system. This issue is patched in version 1.17.1.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web     applications like Jupyter Notebook. Prior to version 1.17.1, if notebook server is started with a value of     `root_dir` that contains the starting user's home directory, then the underlying REST API can be used to     leak the access token assigned at start time by guessing/brute forcing the PID of the jupyter server.
    While this requires an authenticated user session, this URL can be used from a cross-site scripting     payload or from a hooked or otherwise compromised browser to leak this access token to a malicious third     party. This token can be used along with the REST API to interact with Jupyter services/notebooks such as     modifying or overwriting critical files, such as .bashrc or .ssh/authorized_keys, allowing a malicious     user to read potentially sensitive data and possibly gain control of the impacted system. This issue is     patched in version 1.17.1. (CVE-2022-29241)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Jupyter Server provides the backend (i.e. the core services, APIs, and REST endpoints) for Jupyter web
    applications like Jupyter Notebook. Prior to version 1.17.1, if notebook server is started with a value of
    `root_dir` that contains the starting user's home directory, then the underlying REST API can be used to
    leak the access token assigned at start time by guessing/brute forcing the PID of the jupyter server.
    While this requires an authenticated user session, this URL can be used from a cross-site scripting
    payload or from a hooked or otherwise compromised browser to leak this access token to a malicious third
    party. This token can be used along with the REST API to interact with Jupyter services/notebooks such as
    modifying or overwriting critical files, such as .bashrc or .ssh/authorized_keys, allowing a malicious
    user to read potentially sensitive data and possibly gain control of the impacted system. This issue is
    patched in version 1.17.1. (CVE-2022-29241)

ID	Name	Product	Family	Type	Severity
224685	Linux Distros Unpatched Vulnerability : CVE-2022-29241	Nessus	Misc.	Local	high
417988	SCA: security update for jupyter-server (GHSA-q874-g24w-4q9g)	Tenable Cloud Security	SCA Checks	Local	high
417988	SCA: security update for jupyter-server (GHSA-q874-g24w-4q9g)	Tenable Self-Hosted Container Security	SCA Checks	Local	high

Detections

Analytics

CVE-2022-29241

high

Tenable Plugins

high

high

high