NetSight

Security Dashboard

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

Reset
629 matching advisories · page 9 of 21Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2022-30742 Sensitive information exposure vulnerability in FmmExtraOperation of Find My Mobile prior to 7.2.24.12 allows local attackers with log access permissio to get … samsung · find_my_mobile 2022-06-07 low3.3 CVE-2022-30741 Sensitive information exposure vulnerability in SimChangeAlertManger of Find My Mobile prior to 7.2.24.12 allows local attackers with log access permission to … samsung · find_my_mobile 2022-06-07 medium5.0 CVE-2022-22265 Samsung Mobile Devices Use-After-Free VulnerabilityExploited google · android 2022-01-10 medium5.7 CVE-2021-25507 Improper authorization vulnerability in Samsung Flow mobile application prior to 4.8.03.5 allows Samsung Flow PC application connected with user device to acce… samsung · samsung_flow 2021-11-05 low3.3 CVE-2021-25489 Samsung Mobile Devices Improper Input Validation VulnerabilityExploited samsung · android 2021-10-06 high7.3 CVE-2021-25487 Samsung Mobile Devices Out-of-Bounds Read VulnerabilityExploited samsung · android 2021-10-06 medium6.4 CVE-2021-25395 Samsung Mobile Devices Race Condition VulnerabilityExploited samsung · android 2021-06-11 medium6.4 CVE-2021-25394 Samsung Mobile Devices Race Condition VulnerabilityExploited samsung · android 2021-06-11 medium6.1 CVE-2021-25372 Samsung Mobile Devices Improper Boundary Check VulnerabilityExploited samsung · android 2021-03-26 medium6.1 CVE-2021-25371 Samsung Mobile Devices Unspecified VulnerabilityExploited samsung · android 2021-03-26 medium6.1 CVE-2021-25370 Samsung Mobile Devices Memory Corruption VulnerabilityExploited samsung · android 2021-03-26 medium6.2 CVE-2021-25369 Samsung Mobile Devices Improper Access Control VulnerabilityExploited samsung · android 2021-03-26 medium4.4 CVE-2021-25339 Improper address validation in HArx in Samsung mobile devices prior to SMR Mar-2021 Release 1 allows an attacker, given a compromised kernel, to corrupt EL2 me… google · android 2021-03-04 medium4.4 CVE-2021-25338 Improper memory access control in RKP in Samsung mobile devices prior to SMR Mar-2021 Release 1 allows an attacker, given a compromised kernel, to write certai… google · android 2021-03-04 medium4.4 CVE-2021-25337 Samsung Mobile Devices Improper Access Control VulnerabilityExploited samsung · android 2021-03-04 low2.8 CVE-2021-25336 Improper access control in NotificationManagerService in Samsung mobile devices prior to SMR Mar-2021 Release 1 allows untrusted applications to acquire notifi… google · android 2021-03-04 low2.5 CVE-2021-25335 Improper lockscreen status check in cocktailbar service in Samsung mobile devices prior to SMR Mar-2021 Release 1 allows unauthenticated users to access hidden… samsung · one_ui, google · android 2021-03-04 medium5.5 CVE-2021-25334 Improper input check in wallpaper service in Samsung mobile devices prior to SMR Feb-2021 Release 1 allows untrusted application to cause permanent denial of s… google · android 2021-03-04 medium5.5 CVE-2021-22495 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), Q(10.0), and R(11.0) (Exynos chipsets) software. google · android 2021-01-05 medium5.5 CVE-2021-22494 An issue was discovered in the fingerprint scanner on Samsung Note20 mobile devices with Q(10.0) software. google · android 2021-01-05 high8.8 CVE-2021-22492 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) (Broadcom Bluetooth chipsets) software. google · android 2021-01-05 high7.5 CVE-2020-35553 An issue was discovered on Samsung mobile devices with Q(10.0) and R(11.0) (Qualcomm SM8250 chipsets) software. google · android 2020-12-18 medium5.3 CVE-2020-35552 An issue was discovered in the GPS daemon on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) (non-Qualcomm chipsets) software. google · android 2020-12-18 critical9.8 CVE-2020-35551 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-12-18 critical9.8 CVE-2020-35550 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), Q(10.0), and R(11.0) software. google · android 2020-12-18 medium5.5 CVE-2020-35549 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) software. google · android 2020-12-18 medium5.5 CVE-2020-35548 An issue was discovered in Finder on Samsung mobile devices with Q(10.0) software. google · android 2020-12-18 high7.8 CVE-2020-28343 An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) (Exynos 980, 9820, and 9830 chipsets) software. google · android 2020-11-08 high7.8 CVE-2020-28342 An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) (China / India) software. google · android 2020-11-08 high7.8 CVE-2020-28341 An issue was discovered on Samsung mobile devices with Q(10.0) (Exynos990 chipsets) software. google · android 2020-11-08

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.