CVE-2022-29241 Vulnerability Analysis & Exploit Details

CVE-2022-29241
Vulnerability Scoring

7.1
/10
Very High Risk

Highly exploitable, CVE-2022-29241 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2022-29241 Details

Status: Modified

Last updated: 🕡 21 Nov 2024, 06:58 UTC
Originally published on: 🕘 14 Jun 2022, 21:15 UTC

Time between publication and last update: 890 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

CVE-2022-29241 Vulnerability Summary

CVE-2022-29241: 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.

Assessing the Risk of CVE-2022-29241

Access Complexity Graph

The exploitability of CVE-2022-29241 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-29241

This vulnerability, CVE-2022-29241, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-29241, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-29241, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2022-29241 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2022-29241 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2022-29241 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.095% (probability of exploit)

EPSS Percentile: 42.26% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 57.74% of others.

CVE-2022-29241 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:jupyter:jupyter_server:-:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:-:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc10:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc10:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc11:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc11:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc12:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc12:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc13:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc13:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc14:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc14:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc15:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc15:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc16:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc16:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc6:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc6:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc7:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc7:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc8:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc8:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc9:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.0:rc9:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:jupyter:jupyter_server:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:jupyter:jupyter_server:1.1.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-29241: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...