Security readout for executives and security teams
Plain-English summary
Older Jupyter Notebook versions could let a malicious directory name trigger browser-side script execution when viewed in the Notebook file tree. This mainly matters where Notebook is shared or where untrusted users can create folders. The record does not show active exploitation or a CVSS score.
Executive priority
Prioritize remediation for shared or externally reachable Notebook environments. For single-user, trusted local deployments, urgency is lower, but the affected version is very old and should be retired during normal vulnerability cleanup.
Technical view
Jupyter Notebook before 5.7.2 allowed XSS because notebook/static/tree/js/notebooklist.js handled certain URLs unsafely. The attack vector cited is a crafted directory name. The provided sources do not include CVSS, CWE mapping, or complete exploitation prerequisites.
Likely exposure
Exposure is most likely in legacy Jupyter Notebook deployments older than 5.7.2, especially shared, multi-user, teaching, lab, or internal analytics environments where users can create directories visible to others.
Exploitation context
The source bundle does not indicate known active exploitation, and KEV is false. Successful abuse appears to require influencing a directory name and having a user view it through the affected Notebook tree UI. Exact privileges and browser impact are not fully documented in the supplied sources.
Researcher notes
The public record is sparse: no CVSS, CWE, affected CPE, or detailed patch advisory is present in the supplied bundle. Analysis should remain tied to the stated affected range, XSS class, and upstream references.
Mitigation direction
- Upgrade Jupyter Notebook to version 5.7.2 or later.
- Check current vendor and Jupyter release guidance before deploying changes.
- Limit Notebook access to trusted users until upgraded.
- Restrict untrusted write access in shared Notebook workspaces.
Validation and detection
- Inventory Jupyter Notebook package versions across servers and images.
- Confirm no deployed Notebook version is earlier than 5.7.2.
- Review shared workspaces where untrusted users can create directories.
- Verify dependency lockfiles and container images reference the remediated version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2018-19352 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jupyter/notebook/commit/288b73e1edbf527740e273fcc69b889460871648CVE reference · x_refsource_MISC
- https://pypi.org/project/notebook/#historyCVE reference · x_refsource_MISC
- https://github.com/jupyter/notebook/blob/master/docs/source/changelog.rstCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.