NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
131 matching advisories · page 4 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2023-39968 Open Redirect Vulnerability in jupyter-server pip · jupyter-server 2023-08-28 medium4.6 CVE-2023-35394 Azure HDInsight Jupyter Notebook Spoofing Vulnerability microsoft · azure_hdinsight 2023-08-08 high8.8 CVE-2022-39286 Execution with Unnecessary Privileges in JupyterApp pip · jupyter-core 2022-10-26 medium6.4 CVE-2022-2428 A crafted tag in the Jupyter Notebook viewer in GitLab EE/CE affecting all versions before 15.1.6, 15.2 to 15.2.4, and 15.3 to 15.3.2 allows an attacker to iss… gitlab · gitlab 2022-10-17 high7.8 CVE-2022-41083 Visual Studio Code Elevation of Privilege Vulnerability microsoft · jupyter, Microsoft · Jupyter Extension for Visual Studio Code 2022-10-11 high7.5 CVE-2021-32862 nbconvert vulnerable to cross-site scripting (XSS) via multiple exploit paths pip · nbconvert 2022-08-10 high7.1 CVE-2022-29241 Jupyter server Token bruteforcing pip · jupyter-server 2022-06-14 medium4.3 CVE-2022-29238 Jupyter Notebook is a web-based notebook environment for interactive computing. pip · notebook 2022-06-14 medium4.2 CVE-2022-31027 Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator oauthenticator pip · oauthenticator 2022-06-06 high7.5 CVE-2022-24758 Sensitive Auth & Cookie data stored in Jupyter server logs pip · notebook 2022-03-31 high7.7 CVE-2022-0427 Missing sanitization of HTML attributes in Jupyter notebooks in all versions of GitLab CE/EE since version 14.5 allows an attacker to perform arbitrary HTTP PO… gitlab · gitlab 2022-03-28 high7.5 CVE-2022-24757 Insertion of Sensitive Information into Log File in Jupyter notebook pip · jupyter-server 2022-03-23 medium6.3 CVE-2022-21697 SSRF vulnerability in jupyter-server-proxy pip · jupyter-server-proxy 2022-01-25 medium5.4 CVE-2021-29867 IBM Cognos Analytics 11.1.7 and 11.2.0 could allow an authenticated to view or edit a Jupyter notebook that they should not have access to. ibm · cognos_analytics, netapp · oncommand_insight 2021-12-03 medium3.5 CVE-2021-41247 JupyterHub is an open source multi-user server for Jupyter notebooks. pip · jupyterhub 2021-11-04 high8.7 CVE-2021-41134 Stored XSS in Jupyter nbdime pip · nbdime, npm · nbdime, npm · nbdime-jupyterlab 2021-11-03 critical9.1 CVE-2021-41194 Improper Access Control in jupyterhub-firstuseauthenticator pip · jupyterhub-firstuseauthenticator 2021-10-28 critical9.6 CVE-2021-39159 remote code execution via git repo provider pip · binderhub 2021-08-25 critical9.6 CVE-2021-39160 Code injection in nbgitpuller pip · nbgitpuller 2021-08-25 critical10.0 CVE-2021-32798 Special Element Injection in notebook pip · notebook 2021-08-09 high7.4 CVE-2021-32797 JupyterLab: XSS due to lack of sanitization of the action attribute of an html <form> pip · jupyterlab, pip · notebook 2021-08-09 medium5.4 CVE-2021-27225 In Dataiku DSS before 8.0.6, insufficient access control in the Jupyter notebooks integration allows users (who have coding permissions) to read and overwrite … dataiku · data_science_studio 2021-03-01 medium4.5 CVE-2020-36191 Cross-Site Request Forgery in JupyterHub pip · jupyterhub 2021-01-13 medium6.1 CVE-2020-26275 Jupyter Server open redirect vulnerability pip · jupyter-server 2020-12-21 high7.9 CVE-2020-26261 user-readable api tokens in systemd units for JupyterHub pip · jupyterhub-systemdspawner 2020-12-09 high6.3 CVE-2020-26250 Base class whitelist configuration ignored in OAuthenticator pip · oauthenticator 2020-12-01 medium4.1 CVE-2020-26232 Open redirect in Jupyter Server pip · jupyter-server 2020-11-24 medium4.4 CVE-2020-26215 Open redirect in Jupyter Notebook pip · notebook 2020-11-18 high7.0 CVE-2020-16977 <p>A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads a Jupyter notebook file. microsoft · visual_studio_code 2020-10-16 high6.8 CVE-2020-15110 Possible pod name collisions in jupyterhub-kubespawner pip · jupyterhub-kubespawner 2020-07-17

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.