LiveActive security incident?Get immediate response
CVE Record

CVE-2022-29241: Known or guessable hidden files may be accessed in Jupyter Server

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.

HighCVSS 7.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A vulnerable Jupyter Server can expose its startup access token when configured with a root directory that includes the user's home directory. An attacker still needs an authenticated session and user/browser involvement, but token disclosure can lead to file reads, file modification, and possible system control.

Executive priority

Prioritize remediation for shared, internet-accessible, or sensitive-data Jupyter environments. The issue is not described as actively exploited, but token exposure can escalate quickly to data theft, file tampering, and host compromise.

Technical view

Jupyter Server before 1.17.1 is affected by CWE-200. With specific root_dir placement, the REST API may expose hidden files including the server access token through PID guessability. The token can authorize Jupyter API actions against notebooks and files. CVSS is 7.1 high.

Likely exposure

Exposure is most likely in Jupyter Server deployments below 1.17.1 where root_dir contains the starting user's home directory and users authenticate through browser-based Jupyter sessions.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires an authenticated user session and user/browser interaction, such as an XSS payload or compromised browser, then token abuse through Jupyter APIs.

Researcher notes

The strongest evidence is the GitHub advisory and CVE record. Conditions matter: affected version, root_dir including the user's home directory, authenticated session, and browser/user interaction. Do not assume all Jupyter Notebook deployments are exposed without confirming Jupyter Server version and configuration.

Mitigation direction

  • Upgrade Jupyter Server to version 1.17.1 or later.
  • Check the Jupyter advisory for supported backport guidance if upgrades are constrained.
  • Review root_dir configuration so it does not expose the service user's home directory.
  • Restrict Jupyter access to trusted users and isolate notebook hosts.
  • Review related applications for XSS risks affecting authenticated Jupyter sessions.

Validation and detection

  • Inventory Jupyter Server deployments and record jupyter_server package versions.
  • Confirm no reachable deployment runs a version below 1.17.1.
  • Review startup configuration for root_dir placement relative to the service user's home.
  • Check logs and file history for unexpected notebook or filesystem modifications.
  • Verify authenticated Jupyter access is limited to intended users.
Prepared
Confidence
high
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-29241 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2022-29241Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
jupyter-serverjupyter_server< 1.17.1Listed
Weakness

CWE details

CWE-200

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.