CVE-2021-32798: Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in notebook
jupyter · notebook
Affected: jupyter notebook · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 82% of scored CVEs
DescriptionCVE.org
The Jupyter notebook is a web-based notebook environment for interactive computing. In affected versions untrusted notebook can execute code on load. Jupyter Notebook uses a deprecated version of Google Caja to sanitize user inputs. A public Caja bypass can be used to trigger an XSS when a victim opens a malicious ipynb document in Jupyter Notebook. The XSS allows an attacker to execute arbitrary code on the victim computer using Jupyter APIs.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- jupyter · notebook>= 6.0.0, < 6.4.1; < 5.7.11
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Cross-site Scripting
- Vendor
- jupyter
- Published
- August 2021
CoverageNo articles yet
No CyberSIXT article names CVE-2021-32798 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.