NetSight

Security Dashboard

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

Reset
403 matching advisories · page 10 of 14Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2022-2129 Out-of-bounds Write in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora, debian · debian_linux 2022-06-19 high7.8 CVE-2022-2126 Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. vim · vim, debian · debian_linux, fedoraproject · fedora +1 2022-06-19 high7.8 CVE-2022-2125 Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora, apple · macos 2022-06-19 high7.8 CVE-2022-2124 Buffer Over-read in GitHub repository vim/vim prior to 8.2. vim · vim, debian · debian_linux, fedoraproject · fedora +1 2022-06-19 critical GHSA-mphj-rfgv-x4w5 Malware in vimeo_depth_playerMalware npm · vimeo_depth_player 2022-06-13 critical GHSA-j8f5-r44x-pr4m Malware in aframe-vimeo-componentMalware npm · aframe-vimeo-component 2022-06-13 critical GHSA-23f3-q86g-69r2 Malware in vimeo-threejs-playerMalware npm · vimeo-threejs-player 2022-06-13 high7.8 CVE-2022-2042 Use After Free in GitHub repository vim/vim prior to 8.2. vim · vim, apple · macos 2022-06-10 high7.8 CVE-2022-2000 Out-of-bounds Write in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora, apple · macos +1 2022-06-09 high7.8 CVE-2022-1968 Use After Free in GitHub repository vim/vim prior to 8.2. vim · vim, debian · debian_linux, apple · macos 2022-06-02 high7.8 CVE-2022-1942 Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora, apple · macos +1 2022-05-31 high7.8 CVE-2022-1927 Buffer Over-read in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora, apple · macos 2022-05-29 high7.8 CVE-2022-1897 Out-of-bounds Write in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora, apple · macos +1 2022-05-27 high7.8 CVE-2022-1898 Use After Free in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora, debian · debian_linux +1 2022-05-27 high7.8 CVE-2022-1886 Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora 2022-05-26 high7.8 CVE-2022-1851 Out-of-bounds Read in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora, debian · debian_linux +1 2022-05-25 high7.8 CVE-2022-1796 Use After Free in GitHub repository vim/vim prior to 8.2.4979. vim · vim 2022-05-19 high7.8 CVE-2022-1785 Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.4977. vim · vim, debian · debian_linux 2022-05-19 medium5.5 CVE-2022-1771 Uncontrolled Recursion in GitHub repository vim/vim prior to 8.2.4975. vim · vim 2022-05-18 high7.8 CVE-2022-1735 Classic Buffer Overflow in GitHub repository vim/vim prior to 8.2.4969. vim · vim, apple · macos 2022-05-17 high7.8 CVE-2022-1769 Buffer Over-read in GitHub repository vim/vim prior to 8.2.4974. vim · vim, fedoraproject · fedora, apple · macos 2022-05-17 high7.8 CVE-2022-1733 Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4968. vim · vim, fedoraproject · fedora, apple · macos 2022-05-17 medium5.5 CVE-2022-1725 NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2.4959. vim · vim, apple · macos, vim · vim/vim 2022-05-16 medium5.5 CVE-2022-1674 NULL Pointer Dereference in function vim_regexec_string at regexp.c:2733 in GitHub repository vim/vim prior to 8.2.4938. vim · vim, fedoraproject · fedora, apple · macos 2022-05-12 high7.8 CVE-2022-1629 Buffer Over-read in function find_next_quote in GitHub repository vim/vim prior to 8.2.4925. vim · vim, fedoraproject · fedora, apple · macos 2022-05-10 high7.8 CVE-2022-1621 Heap buffer overflow in vim_strncpy find_word in GitHub repository vim/vim prior to 8.2.4919. vim · vim, debian · debian_linux, fedoraproject · fedora +1 2022-05-10 high7.5 CVE-2022-1620 NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 in GitHub repository vim/vim prior to 8.2.4901. vim · vim, fedoraproject · fedora, apple · macos 2022-05-08 high7.8 CVE-2022-1619 Heap-based Buffer Overflow in function cmdline_erase_chars in GitHub repository vim/vim prior to 8.2.4899. vim · vim, fedoraproject · fedora, debian · debian_linux +3 2022-05-08 high7.8 CVE-2022-1616 Use after free in append_command in GitHub repository vim/vim prior to 8.2.4895. vim · vim, fedoraproject · fedora, debian · debian_linux +1 2022-05-07 high7.8 CVE-2022-20732 A vulnerability in the configuration file protections of Cisco Virtualized Infrastructure Manager (VIM) could allow an authenticated, local attacker to access … cisco · virtualized_infrastructure_manager 2022-04-21

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.