NetSight

Security Dashboard

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

Reset
230 matching advisories · page 3 of 8Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2019-19553 In Wireshark 3.0.0 to 3.0.6 and 2.6.0 to 2.6.12, the CMS dissector could crash. wireshark · wireshark, opensuse · leap, oracle · solaris +2 2019-12-05 high7.5 CVE-2019-16319 In Wireshark 3.0.0 to 3.0.3 and 2.6.0 to 2.6.10, the Gryphon dissector could go into an infinite loop. wireshark · wireshark, opensuse · leap, debian · debian_linux 2019-09-15 high7.5 CVE-2019-13619 In Wireshark 3.0.0 to 3.0.2, 2.6.0 to 2.6.9, and 2.4.0 to 2.4.15, the ASN.1 BER dissector and related dissectors could crash. wireshark · wireshark, fedoraproject · fedora, canonical · ubuntu_linux +2 2019-07-17 high7.5 CVE-2019-12295 In Wireshark 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14, the dissection engine could crash. wireshark · wireshark, debian · debian_linux, canonical · ubuntu_linux +9 2019-05-23 high7.5 CVE-2019-10903 In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the DCERPC SPOOLSS dissector could crash. wireshark · wireshark, fedoraproject · fedora, debian · debian_linux +2 2019-04-09 high7.5 CVE-2019-10902 In Wireshark 3.0.0, the TSDNS dissector could crash. wireshark · wireshark, fedoraproject · fedora 2019-04-09 high7.5 CVE-2019-10901 In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the LDSS dissector could crash. wireshark · wireshark, fedoraproject · fedora, debian · debian_linux +2 2019-04-09 high7.5 CVE-2019-10900 In Wireshark 3.0.0, the Rbm dissector could go into an infinite loop. wireshark · wireshark, fedoraproject · fedora 2019-04-09 high7.5 CVE-2019-10899 In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the SRVLOC dissector could crash. wireshark · wireshark, fedoraproject · fedora, debian · debian_linux +2 2019-04-09 high7.5 CVE-2019-10898 In Wireshark 3.0.0, the GSUP dissector could go into an infinite loop. wireshark · wireshark, fedoraproject · fedora 2019-04-09 high7.5 CVE-2019-10897 In Wireshark 3.0.0, the IEEE 802.11 dissector could go into an infinite loop. wireshark · wireshark, fedoraproject · fedora 2019-04-09 high7.5 CVE-2019-10896 In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the DOF dissector could crash. wireshark · wireshark, fedoraproject · fedora, opensuse · leap +2 2019-04-09 high7.5 CVE-2019-10895 In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the NetScaler file parser could crash. wireshark · wireshark, fedoraproject · fedora, debian · debian_linux +2 2019-04-09 high7.5 CVE-2019-10894 In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the GSS-API dissector could crash. wireshark · wireshark, fedoraproject · fedora, debian · debian_linux +2 2019-04-09 high7.5 CVE-2019-9214 In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. wireshark · wireshark, debian · debian_linux 2019-02-28 high7.5 CVE-2019-9208 In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the TCAP dissector could crash. wireshark · wireshark, debian · debian_linux 2019-02-28 high7.5 CVE-2018-19628 In Wireshark 2.6.0 to 2.6.4, the ZigBee ZCL dissector could crash. wireshark · wireshark, debian · debian_linux 2018-11-29 high7.5 CVE-2018-19627 In Wireshark 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10, the IxVeriWave file parser could crash. wireshark · wireshark, debian · debian_linux 2018-11-29 high7.5 CVE-2018-19623 In Wireshark 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10, the LBMPDM dissector could crash. wireshark · wireshark, debian · debian_linux 2018-11-29 high7.5 CVE-2018-19622 In Wireshark 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10, the MMSE dissector could go into an infinite loop. wireshark · wireshark, debian · debian_linux 2018-11-29 high7.5 CVE-2018-18227 In Wireshark 2.6.0 to 2.6.3 and 2.4.0 to 2.4.9, the MS-WSP protocol dissector could crash. wireshark · wireshark, debian · debian_linux 2018-10-12 high7.5 CVE-2018-18226 In Wireshark 2.6.0 to 2.6.3, the Steam IHS Discovery dissector could consume system memory. wireshark · wireshark, debian · debian_linux 2018-10-12 high7.5 CVE-2018-18225 In Wireshark 2.6.0 to 2.6.3, the CoAP dissector could crash. wireshark · wireshark, debian · debian_linux, opensuse · leap 2018-10-12 high7.5 CVE-2018-16058 In Wireshark 2.6.0 to 2.6.2, 2.4.0 to 2.4.8, and 2.2.0 to 2.2.16, the Bluetooth AVDTP dissector could crash. wireshark · wireshark, debian · debian_linux 2018-08-30 high7.5 CVE-2018-16057 In Wireshark 2.6.0 to 2.6.2, 2.4.0 to 2.4.8, and 2.2.0 to 2.2.16, the Radiotap dissector could crash. wireshark · wireshark, debian · debian_linux 2018-08-30 high7.5 CVE-2018-16056 In Wireshark 2.6.0 to 2.6.2, 2.4.0 to 2.4.8, and 2.2.0 to 2.2.16, the Bluetooth Attribute Protocol dissector could crash. wireshark · wireshark, debian · debian_linux 2018-08-30 high7.5 CVE-2018-14438 In Wireshark through 2.6.2, the create_app_running_mutex function in wsutil/file_util.c calls SetSecurityDescriptorDacl to set a NULL DACL, which allows attack… wireshark · wireshark 2018-07-20 high7.5 CVE-2018-14370 In Wireshark 2.6.0 to 2.6.1 and 2.4.0 to 2.4.7, the IEEE 802.11 protocol dissector could crash. wireshark · wireshark 2018-07-19 high7.5 CVE-2018-14369 In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the HTTP2 dissector could crash. wireshark · wireshark, debian · debian_linux 2018-07-19 high7.5 CVE-2018-14368 In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the Bazaar protocol dissector could go into an infinite loop. wireshark · wireshark, debian · debian_linux 2018-07-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.