NetSight

Security Dashboard

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

Reset
513 matching advisories · page 13 of 18Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2023-38703 PJSIP is a free and open source multimedia communication library written in C with high level API in C, C++, Java, C#, and Python languages. teluu · pjsip 2023-10-06 critical9.8 CVE-2022-48565 An XML External Entity (XXE) issue was discovered in Python through 3.9.1. python · python, debian · debian_linux 2023-08-22 critical9.8 CVE-2023-40267 GitPython vulnerable to remote code execution due to insufficient sanitization of input arguments pip · GitPython 2023-08-11 critical9.8 CVE-2018-25082 weixin-python XML External Entity vulnerability pip · weixin-python 2023-03-21 critical9.0 CVE-2023-25617 SAP Cloud SDK for AI Python has OS Command Injection when Program Objects Execution is Enabled pip · sap-ai-sdk-base 2023-03-14 critical9.8 CVE-2023-24107 hour_of_code_python_2015 commit 520929797b9ca43bb818b2e8f963fb2025459fa3 was discovered to contain a code execution backdoor via the request package (requireme… hour_of_code_python_2015_project · hour_of_code_python_2015 2023-02-22 critical GHSA-3xgq-whx6-qgrw Malware in python-tdigest-bindingsMalware npm · python-tdigest-bindings 2023-01-30 critical GHSA-785w-pm5r-v33g Malware in python-statface-clientMalware npm · python-statface-client 2023-01-30 critical9.2 CVE-2022-46179 LiuOS is a small Python project meant to imitate the functions of a regular operating system. liuos_project · liuos 2022-12-28 critical9.8 CVE-2022-46609 Python3-RESTfulAPI commit d9907f14e9e25dcdb54f5b22252b0e9452e3970e and e772e0beee284c50946e94c54a1d43071ca78b74 was discovered to contain a code execution back… python3-restfulapi_project · python3-restfulapi 2022-12-14 critical8.1 CVE-2022-24439 GitPython vulnerable to Remote Code Execution due to improper user input validation pip · GitPython 2022-12-06 critical9.8 CVE-2022-44054 The d8s-xml for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-xml 2022-11-07 critical9.8 CVE-2022-44053 The d8s-networking for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-networking 2022-11-07 critical9.8 CVE-2022-44052 The d8s-dates for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-dates 2022-11-07 critical9.8 CVE-2022-44051 The d8s-stats for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-stats 2022-11-07 critical9.8 CVE-2022-44050 The d8s-networking for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-networking 2022-11-07 critical9.8 CVE-2022-44049 The d8s-python for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-python 2022-11-07 critical9.8 CVE-2022-44048 The d8s-urls for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-urls 2022-11-07 critical9.8 CVE-2022-43305 The d8s-python for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-python 2022-11-07 critical9.8 CVE-2022-43304 The d8s-timer for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-timer 2022-11-07 critical9.8 CVE-2022-43303 The d8s-strings for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-strings 2022-11-07 critical9.8 CVE-2022-37454 Buffer overflow in sponge queue functions pip · pysha3, rubygems · sha3 2022-10-21 critical9.8 CVE-2022-42044 The d8s-asns package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-asns 2022-10-11 critical9.8 CVE-2022-42043 The d8s-xml package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-xml 2022-10-11 critical9.8 CVE-2022-42042 The d8s-networking package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-networking 2022-10-11 critical9.8 CVE-2022-42041 The d8s-file-system package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-file-system 2022-10-11 critical9.8 CVE-2022-42040 The d8s-algorithms package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-algorithms 2022-10-11 critical9.8 CVE-2022-42039 The d8s-lists package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-lists 2022-10-11 critical9.8 CVE-2022-42038 The d8s-ip-addresses package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-ip-addresses 2022-10-11 critical9.8 CVE-2022-42037 The d8s-asns package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. democritus · d8s-asns 2022-10-11

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.