NetSight

Security Dashboard

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

Reset
513 matching advisories · page 14 of 18Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2022-42036 The d8s-urls package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-urls 2022-10-11 critical9.8 CVE-2022-41387 The d8s-pdfs package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-pdfs 2022-10-11 critical9.8 CVE-2022-41386 The d8s-utility package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-utility 2022-10-11 critical9.8 CVE-2022-41385 The d8s-html package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-html 2022-10-11 critical9.8 CVE-2022-41384 The d8s-domains package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-domains 2022-10-11 critical9.8 CVE-2022-41383 The d8s-archives package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-archives 2022-10-11 critical9.8 CVE-2022-41382 The d8s-json package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-json 2022-10-11 critical9.8 CVE-2022-41381 The d8s-utility package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-utility 2022-10-11 critical9.8 CVE-2022-41380 The d8s-yaml package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-yaml 2022-10-11 critical9.1 CVE-2022-39227 python-jwt vulnerable to token forgery with new claims pip · python-jwt 2022-09-21 critical9.9 CVE-2022-28802 Code by Zapier before 2022-08-17 allowed intra-account privilege escalation that included execution of Python or JavaScript code. zapier · code_by_zapier 2022-09-21 critical9.8 CVE-2022-40812 The d8s-pdfs for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus_pdfs_project · democritus_pdfs 2022-09-19 critical9.8 CVE-2022-40810 The d8s-ip-addresses for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus_ip_addresses_project · democritus_ip_addresses 2022-09-19 critical9.8 CVE-2022-40809 The d8s-dicts for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus_dicts_project · democritus_dicts 2022-09-19 critical9.8 CVE-2022-40432 The d8s-strings for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-strings_project · d8s-strings 2022-09-19 critical9.8 CVE-2022-40431 The d8s-pdfs for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-pdfs_project · d8s-pdfs 2022-09-19 critical9.8 CVE-2022-40430 The d8s-utility for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-utility_project · d8s-utility 2022-09-19 critical9.8 CVE-2022-40429 The d8s-ip-addresses for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-ip-addresses_project · d8s-ip-addresses 2022-09-19 critical9.8 CVE-2022-40428 The d8s-mpeg for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-mpeg_project · d8s_mpeg 2022-09-19 critical9.8 CVE-2022-40426 The d8s-asns for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-asns_project · d8s-asns 2022-09-19 critical9.8 CVE-2022-40425 The d8s-html for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-html_project · d8s-html 2022-09-19 critical9.8 CVE-2022-38887 The d8s-python for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-python_project · d8s-python 2022-09-19 critical9.8 CVE-2022-38886 The d8s-xml for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-xml_project · d8s-xml 2022-09-19 critical9.8 CVE-2022-38885 The d8s-netstrings for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-netstrings_project · d8s-netstrings 2022-09-19 critical9.8 CVE-2022-38884 The d8s-grammars for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-grammars_project · d8s-grammars 2022-09-19 critical9.8 CVE-2022-38883 The d8s-math for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-math_project · d8s-math 2022-09-19 critical9.8 CVE-2022-38882 The d8s-json for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-json_project · d8s-json 2022-09-19 critical9.8 CVE-2022-38881 The d8s-archives for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. d8s-archives_project · d8s-archives 2022-09-19 critical9.8 CVE-2022-40811 The d8s-urls for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus_urls_project · democritus_urls 2022-09-19 critical9.8 CVE-2022-40808 The d8s-dates for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus_dates_project · democritus_dates 2022-09-19

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.