CVE-2022-29241: Jupyter server Jupyter Server Token Bruteforcing Vulnerability

HIGH
Advisory Identifier: GHSA-q874-g24w-4q9g
CVSS 7.1
Published
Advisory Summary

CVE-2022-29241 is a HIGH (CVSS 7.1) jupyter server token bruteforcing vulnerability (General Security Weakness) affecting Jupyter server libraries in the PyPI ecosystem. The issue involves jupyter server token bruteforcing. Remediation is available by upgrading affected packages to version 1.17.1, 2.0.0a1.

CVE-2022-29241 at a Glance

CVE Identifier CVE-2022-29241
GHSA Identifier GHSA-q874-g24w-4q9g
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification General Security Weakness
Affected Product Jupyter server
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2022-29241

To remediate this vulnerability, upgrade all affected Jupyter server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

jupyter-server fixed: 1.17.1
pip install jupyter-server>=1.17.1
jupyter-server fixed: 2.0.0a1
pip install jupyter-server>=2.0.0a1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show jupyter-server

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2022-29241, inspect your installed packages using pip:

pip show jupyter-server

Analyze the terminal output to locate any version of Jupyter server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.17.1), your application is affected.

Note: The pip show jupyter-server command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Jupyter server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Affects: Notebook and Lab between 6.4.0?(potentially earlier) and 6.4.11 (currently latest). Jupyter Server <=1.16.0. If I am correct about the responsible code it will affect Jupyter-Server 1.17.0 and 2.0.0a0 as well. Description: 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 an xss payload (as in CVE-2021-32798) 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.

CVE-2022-29241 Affected Jupyter server Versions

2 component(s)
Fixed Versions:
1.17.12.0.0a1
Product / Package Ecosystem Affected Versions Fixed Version
jupyter-server
PyPI
< 1.17.1
1.17.1
jupyter-server
PyPI
≥ 2.0.0a0
< 2.0.0a1
All 1 versions
2.0.0a0
2.0.0a1

References

Frequently Asked Questions

What is CVE-2022-29241?
CVE-2022-29241 is a security vulnerability in Jupyter server involving Jupyter server Token bruteforcing under General Security Weakness.
Which Jupyter server versions are affected?
Affected versions include releases prior to 1.17.1, 2.0.0a1 across affected packages: jupyter-server.
What version fixes CVE-2022-29241?
Upgrading to 1.17.1, 2.0.0a1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is jupyter-server affected?
Yes, jupyter-server is affected in releases prior to 1.17.1, 2.0.0a1. Upgrade your dependency to 1.17.1, 2.0.0a1 or later.
What is the CVSS score of CVE-2022-29241?
CVE-2022-29241 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2022-29241?
CVE-2022-29241 is classified under General Security Weakness.
How can I check PyPI dependencies for CVE-2022-29241?
Run the dependency tree command: 'pip show jupyter-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q874-g24w-4q9g",
  "modified" : "2023-10-26T13:29:37Z",
  "published" : "2022-06-16T23:13:57Z",
  "aliases" : [ "CVE-2022-29241" ],
  "summary" : "Jupyter server Token bruteforcing",
  "details" : "Affects: Notebook and Lab between 6.4.0?(potentially earlier) and 6.4.11 (currently latest). Jupyter Server <=1.16.0. If I am correct about the responsible code it will affect Jupyter-Server 1.17.0 and 2.0.0a0 as well.\nDescription: 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 an xss payload (as in CVE-2021-32798) 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.\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyter-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.17.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyter-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0a0"
      }, {
        "fixed" : "2.0.0a1"
      } ]
    } ],
    "versions" : [ "2.0.0a0" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-q874-g24w-4q9g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-29241"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyter-server/jupyter_server/commit/3485007abbb459585357212dcaa20521989272e8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyter-server/jupyter_server/commit/877da10cd0d7ae45f8b1e385fa1f5a335e7adf1f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jupyter-server/jupyter_server"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/jupyter-server/PYSEC-2022-211.yaml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-06-16T23:13:57Z",
    "nvd_published_at" : "2022-06-14T21:15:00Z"
  }
}