NetSight

Security Dashboard

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

Reset
122 matching advisories · page 4 of 5Index updated 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2022-2874 NULL Pointer Dereference in GitHub repository vim/vim prior to 9.0.0224. vim · vim, vim · vim/vim 2022-08-18 medium6.5 CVE-2022-2598 Out-of-bounds Write to API in GitHub repository vim/vim prior to 9.0.0100. vim · vim, debian · debian_linux 2022-08-01 medium5.5 CVE-2022-2231 NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2. vim · vim, fedoraproject · fedora 2022-06-28 medium5.5 CVE-2022-2208 NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2.5163. vim · vim, fedoraproject · fedora 2022-06-27 medium5.5 CVE-2022-1771 Uncontrolled Recursion in GitHub repository vim/vim prior to 8.2.4975. vim · vim 2022-05-18 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 medium5.5 CVE-2022-1420 Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4774. vim · vim, fedoraproject · fedora, apple · macos 2022-04-21 medium5.5 CVE-2022-0714 Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436. vim · vim, fedoraproject · fedora, debian · debian_linux +1 2022-02-22 medium5.5 CVE-2022-0696 NULL Pointer Dereference in GitHub repository vim/vim prior to 8.2.4428. vim · vim, fedoraproject · fedora, apple · macos +1 2022-02-21 medium5.5 CVE-2022-0319 Out-of-bounds Read in vim/vim prior to 8.2. vim · vim, debian · debian_linux, apple · macos 2022-01-21 medium6.6 CVE-2022-0213 vim is vulnerable to Heap-based Buffer Overflow vim · vim, debian · debian_linux 2022-01-14 medium5.5 CVE-2022-0156 vim is vulnerable to Use After Free vim · vim, fedoraproject · fedora, apple · macos 2022-01-10 medium5.5 CVE-2021-4193 vim is vulnerable to Out-of-bounds Read vim · vim, fedoraproject · fedora, debian · debian_linux +2 2021-12-31 medium5.5 CVE-2021-3875 vim is vulnerable to Heap-based Buffer Overflow vim · vim, fedoraproject · fedora 2021-10-15 medium5.3 CVE-2019-20807 In Vim before 8.1.0881, users can circumvent the rvim restricted mode and execute arbitrary OS commands via scripting interfaces (e.g., Python, Ruby, or Lua). vim · vim, debian · debian_linux, opensuse · leap +4 2020-05-28 medium5.3 CVE-2019-14957 The JetBrains Vim plugin before version 0.52 was storing individual project data in the global vim_settings.xml file. jetbrains · vim 2019-10-01 medium5.3 CVE-2017-6020 Leao Consultoria e Desenvolvimento de Sistemas (LCDS) LTDA ME LAquis SCADA software versions prior to version 4.1.0.3237 do not neutralize external input to en… lcds · laquis_scada 2018-04-17 medium6.1 CVE-2016-10706 The Jetpack plugin before 4.0.3 for WordPress has XSS via a crafted Vimeo link. automattic · jetpack 2018-01-12 medium5.5 CVE-2017-17087 fileio.c in Vim prior to 8.0.1263 sets the group ownership of a .swp file to the editor's primary group (which may be different from the group ownership of the… vim · vim, debian · debian_linux, canonical · ubuntu_linux 2017-12-01 medium5.5 CVE-2017-1000382 VIM version 8.0.1187 (and other versions most likely) ignores umask when creating a swap file ("[ORIGINAL_FILENAME].swp") resulting in files that may be world … vim · vim 2017-10-31 medium5.4 CVE-2017-5870 Multiple cross-site scripting (XSS) vulnerabilities in ViMbAdmin 3.0.15 allow remote attackers to inject arbitrary web script or HTML via the (1) domain or (2)… composer · opensolutions/vimbadmin 2017-05-23 medium6.5 CVE-2017-8355 In ImageMagick 7.0.5-5, the ReadMTVImage function in mtv.c allows attackers to cause a denial of service (memory leak) via a crafted file. imagemagick · imagemagick, debian · debian_linux 2017-04-30 medium5.9 CVE-2017-5605 XMPP Clients User Impersonation Vulnerability in Movim Moxl composer · movim/moxl 2017-02-09 medium6.9 CVE-2009-0316 Untrusted search path vulnerability in src/if_python.c in the Python interface in Vim before 7.2.045 allows local users to execute arbitrary code via a Trojan … vim · vim 2009-01-28 medium4.3 CVE-2008-4677 autoload/netrw.vim (aka the Netrw Plugin) 109, 131, and other versions before 133k for Vim 7.1.266, other 7.1 versions, and 7.2 stores credentials for an FTP s… vim · netrw 2008-10-22 medium6.8 CVE-2008-3432 Heap-based buffer overflow in the mch_expand_wildcards function in os_unix.c in Vim 6.2 and 6.3 allows user-assisted attackers to execute arbitrary code via sh… vim · vim 2008-10-10 medium6.8 CVE-2007-5445 Buffer overflow in the DB Software Laboratory VImpX (VImpAX1) ActiveX control in VImpX.ocx 4.7.3.0 allows remote attackers to execute arbitrary code via a long… db_software_laboratory · vimpx 2007-10-14 medium6.8 CVE-2007-2953 Format string vulnerability in the helptags_one function in src/ex_cmds.c in Vim 6.4 and earlier, and 7.x up to 7.1, allows user-assisted remote attackers to e… vim_development_group · vim 2007-07-31 medium4.6 CVE-2005-0069 The (1) tcltags or (2) vimspell.sh scripts in vim 6.3 allow local users to overwrite or create arbitrary files via a symlink attack on temporary files. vim_development_group · vim 2005-01-13

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.