# CVE-2019-10856: Jupyter Notebook open redirect vulnerability

> An open redirect vulnerability in Jupyter Notebook allows attackers to redirect users to malicious sites via an empty netloc.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rcx2-m7jp-p9wj, PYSEC-2019-158, UBUNTU-CVE-2019-10856

## What is CVE-2019-10856?

CVE-2019-10856 is a medium-severity vulnerability in n/a, published on 4 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In Jupyter Notebook before 5.7.8, an open redirect can occur via an empty netloc. This issue exists because of an incomplete fix for CVE-2019-10255.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2019-10856?

3 open source packages ship an affected version, including notebook. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `notebook` | PyPI | All versions | 5.7.8 |
| `notebook` | PyPI | All versions | 5.7.8 |
| `notebook` | PyPI | All versions | 5.7.8 |

Products: Jupyter Notebook.

## How do I fix CVE-2019-10856?

Upgrade notebook to 5.7.8 or later.

## Is CVE-2019-10856 being exploited?

There is no known exploitation of CVE-2019-10856 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-32798](https://insights.sbomify.com/CVE-2021-32798/): Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in notebook (critical 10.0)
- [CVE-2018-8768](https://insights.sbomify.com/CVE-2018-8768/): Jupyter Notebook file bypasses sanitization, executes JavaScript (high 7.8)
- [CVE-2022-24758](https://insights.sbomify.com/CVE-2022-24758/): Insertion of Sensitive Information into Log File affects Jupyter Notebook (high 7.5)
- [CVE-2018-19351](https://insights.sbomify.com/CVE-2018-19351/): Jupyter Notebook XSS via untrusted notebooks (medium 6.1)
- [CVE-2018-19352](https://insights.sbomify.com/CVE-2018-19352/): Jupyter Notebook XSS via directory name (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10856 and fix it if it is affected.

What it is: CVE-2019-10856 is a medium-severity vulnerability in n/a, published on 4 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10856 in the wild and no public exploit code.

Affected packages and fixed versions:
- notebook (PyPI): affected all versions; fixed in 5.7.8
- notebook (PyPI): affected all versions; fixed in 5.7.8
- notebook (PyPI): affected all versions; fixed in 5.7.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-10856/ (Markdown: https://insights.sbomify.com/CVE-2019-10856/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10856
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10856
- OSV: https://osv.dev/vulnerability/CVE-2019-10856

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-10856/
Summaries are generated and may contain mistakes; the official description above is the record.