NetSight

Security Dashboard

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

Reset
579 matching advisories · page 14 of 20Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2021-25458 NULL pointer dereference vulnerability in ION driver prior to SMR Sep-2021 Release 1 allows attackers to cause memory corruption. google · android 2021-09-09 low3.3 CVE-2021-25455 OOB read vulnerability in libsaviextractor.so library prior to SMR Sep-2021 Release 1 allows attackers to access arbitrary address through pointer via forged a… google · android 2021-09-09 low3.1 CVE-2021-25454 OOB read vulnerability in libsaacextractor.so library prior to SMR Sep-2021 Release 1 allows attackers to execute remote DoS via forged aac file. google · android 2021-09-09 low3.3 CVE-2021-25451 A PendingIntent hijacking in NetworkPolicyManagerService prior to SMR Sep-2021 Release 1 allows attackers to get IMSI data. google · android 2021-09-09 low3.3 CVE-2021-38591 An issue was discovered on LG mobile devices with Android OS P and Q software for mt6762/mt6765/mt6883. google · android 2021-08-12 low2.4 CVE-2021-25409 Improper access in Notification setting prior to SMR JUN-2021 Release 1 allows physically proximate attackers to set arbitrary notification via physically conf… google · android 2021-06-11 low2.3 CVE-2021-25389 Improper running task check in S Secure prior to SMR MAY-2021 Release 1 allows attackers to use locked app without authentication. google · android 2021-06-11 low2.5 CVE-2021-29619 Segfault in `tf.raw_ops.SparseCountSparseOutput` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29618 Crash in `tf.transpose` with complex inputs pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29617 Crash in `tf.strings.substr` due to `CHECK`-fail pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29616 Null dereference in Grappler's `TrySimplify` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29615 Stack overflow in `ParseAttrValue` with nested tensors pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low3.6 CVE-2021-29612 Heap buffer overflow in `BandedTriangularSolve` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low3.6 CVE-2021-29611 Incomplete validation in `SparseReshape` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low3.6 CVE-2021-29610 Invalid validation in `QuantizeAndDequantizeV2` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29604 Division by zero in TFLite's implementation of hashtable lookup pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29603 Heap OOB write in TFLite pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29602 Division by zero in TFLite's implementation of `DepthwiseConv` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29600 Division by zero in TFLite's implementation of `OneHot` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29599 Division by zero in TFLite's implementation of Split pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29598 Division by zero in TFLite's implementation of `SVDF` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29597 Division by zero in TFLite's implementation of `SpaceToBatchNd` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29596 Division by zero in TFLite's implementation of `EmbeddingLookup` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29595 Division by zero in TFLite's implementation of `DepthToSpace` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29594 Division by zero in TFLite's convolution code pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29593 Division by zero in TFLite's implementation of `BatchToSpaceNd` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29590 Heap OOB read in TFLite's implementation of `Minimum` or `Maximum` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29589 Division by zero in TFLite's implementation of `GatherNd` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29588 Division by zero in TFLite's implementation of `TransposeConv` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14 low2.5 CVE-2021-29587 Division by zero in TFLite's implementation of `SpaceToDepth` pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2021-05-14

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.