CVE-2022-29241
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJupyter 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJupyter Server versions before 1.17.1 contain an information disclosure vulnerability where the REST API can leak the access token assigned at server start if the server is started with a root_dir containing the user's home directory. An authenticated attacker can guess/brute-force the server's PID to construct the token-leaking URL, which can then be exploited via XSS or a compromised browser. The leaked token allows full interaction with Jupyter services, including modifying sensitive files like .bashrc or .ssh/authorized_keys for system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.17.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Jupyter Server versionRun 'jupyter server --version' or check the installed package version via pip (pip show jupyter_server). Compare the version number against the affected range (versions before 1.17.1).Affected if The installed version is 1.17.0 or earlier.
-
Determine the root_dir configurationCheck the Jupyter Server startup command or configuration file. Look for the --root-dir parameter used when starting the server, or the c.Server.root_dir setting in jupyter_server_config.py.Affected if A root_dir was explicitly set or defaults to a directory containing the user's home path.
-
Verify root_dir path contains user home directoryExamine the root_dir value set for the server. Check if the path includes or resolves to the user's home directory (such as /home/username, ~, or the user's $HOME path).Affected if The root_dir path contains, starts with, or resolves to the user's home directory.
A user is affected if Jupyter Server version is earlier than 1.17.1 AND the server was started with a root_dir that includes or points to the user's home directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.17.0
Upgrade Jupyter Server to version 1.17.1 or later. Additionally, ensure notebook servers are not started with root_dir pointing to or containing the user's home directory.
Jupyter Server >= 1.17.1
- Upgrade Jupyter Server to version 1.17.1 or later to remediate this vulnerability
- After upgrading, verify that the server starts correctly and all authentication mechanisms work as expected
- If using Jupyter Notebook or other Jupyter web applications that depend on Jupyter Server, ensure those are also compatible with the upgraded version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29241 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29241 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data