NetSight

Security Dashboard

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

Reset
124 matching advisories · page 4 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2019-20583 An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) (with TEEGRIS) software. google · android 2020-03-24 critical9.8 CVE-2019-20582 An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) devices (Exynos9810 chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20581 An issue was discovered on Samsung mobile devices with N(7.x), O(8.x), and P(9.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20578 An issue was discovered on Samsung mobile devices with P(9.0) (Exynos 9820 chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20572 An issue was discovered on Samsung mobile devices with O(8.1) and P(9.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20571 An issue was discovered on Samsung mobile devices with O(8.x) (with TEEGRIS) software. google · android 2020-03-24 critical9.8 CVE-2019-20567 An issue was discovered on Samsung mobile devices with N(7.x), O(8.x), and P(9.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20566 An issue was discovered on Samsung mobile devices with any (before September 2019 for SMP1300 Exynos modem chipsets) software. samsung · exynos_smp1300 2020-03-24 critical9.8 CVE-2019-20563 An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) (with TEEGRIS) software. google · android 2020-03-24 critical9.8 CVE-2019-20562 An issue was discovered on Samsung mobile devices with P(9.0) (with TEEGRIS) software. google · android 2020-03-24 critical9.8 CVE-2019-20561 An issue was discovered on Samsung mobile devices with N(7.x), O(8.x), and P(9.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20560 An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) (with TEEGRIS) software. google · android 2020-03-24 critical9.8 CVE-2019-20558 An issue was discovered on Samsung mobile devices with N(7.x), O(8.x), and P(9.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20556 An issue was discovered on Samsung mobile devices with P(9.0) (SM6150, SM8150, SM8150_FUSION, exynos7885, exynos9610, and exynos9820 chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20553 An issue was discovered on Samsung mobile devices with P(9.0) (SM6150, SM8150, SM8150_FUSION, exynos7885, exynos9610, and exynos9820 chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20549 An issue was discovered on Samsung mobile devices with N(7.x), O(8.x), and P(9.0) (Broadcom chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20548 An issue was discovered on Samsung mobile devices with P(9.0) devices (Qualcomm chipsets) software. google · android 2020-03-24 critical9.8 CVE-2020-10850 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2020-10849 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) (Exynos7885, Exynos8895, and Exynos9810 chipsets) software. google · android 2020-03-24 critical9.8 CVE-2020-10848 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) (Exynos 9810 chipsets) software. google · android 2020-03-24 critical9.8 CVE-2020-10837 An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) (with TEEGRIS) software. google · android 2020-03-24 critical9.8 CVE-2020-10836 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2020-10835 An issue was discovered on Samsung mobile devices with any (before February 2020 for Exynos modem chipsets) software. samsung · exynos 2020-03-24 critical9.8 CVE-2019-20545 An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20544 An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) (Exynos chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20537 An issue was discovered on Samsung mobile devices with P(9.0) (TEEGRIS and Qualcomm chipsets). google · android 2020-03-24 critical9.8 CVE-2019-20536 An issue was discovered on Samsung mobile devices with N(7.1), O(8.x), and P(9.0) (released in China) software. google · android 2020-03-24 critical9.8 CVE-2019-20530 An issue was discovered on Samsung mobile devices with N(7.1), O(8.x), P(9.0), and Q(10.0) software. google · android 2020-03-24 critical9.8 CVE-2018-9143 On Samsung mobile devices with M(6.0) and N(7.x) software, a heap overflow in the sensorhub binder service leads to code execution in a privileged process, aka… samsung · samsung_mobile 2018-03-30 critical9.8 CVE-2018-9139 On Samsung mobile devices with N(7.x) software, a buffer overflow in the vision service allows code execution in a privileged process via a large frame size, a… samsung · samsung_mobile 2018-03-30

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.