NetSight

Security Dashboard

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

Reset
237 matching advisories · page 5 of 8Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2023-37367 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor, and Modem (Exynos 9820, Exynos 980, Exynos 850, Exynos 1080, Exynos 2100, Exy… samsung · exynos_9820_firmware, samsung · exynos_980_firmware, samsung · exynos_850_firmware +9 2023-09-08 medium4.4 CVE-2023-21492 Samsung Mobile Devices Insertion of Sensitive Information Into Log File VulnerabilityExploited samsung · android 2023-05-04 medium6.8 CVE-2023-29091 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor and Modem for Exynos Modem 5123, Exynos Modem 5300, Exynos 980, Exynos 1080, E… samsung · exynos_5300_firmware, samsung · exynos_5123_firmware, samsung · exynos_980_firmware +3 2023-04-14 medium6.8 CVE-2023-29090 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor and Modem for Exynos Modem 5123, Exynos Modem 5300, Exynos 980, Exynos 1080, E… samsung · exynos_5300_firmware, samsung · exynos_5123_firmware, samsung · exynos_980_firmware +3 2023-04-14 medium6.8 CVE-2023-29089 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor and Modem for Exynos Modem 5123, Exynos Modem 5300, Exynos 980, Exynos 1080, E… samsung · exynos_5300_firmware, samsung · exynos_5123_firmware, samsung · exynos_980_firmware +3 2023-04-14 medium6.8 CVE-2023-29088 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor and Modem for Exynos Modem 5123, Exynos Modem 5300, Exynos 980, Exynos 1080, E… samsung · exynos_5300_firmware, samsung · exynos_5123_firmware, samsung · exynos_980_firmware +3 2023-04-14 medium6.8 CVE-2023-29087 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor and Modem for Exynos Modem 5123, Exynos Modem 5300, Exynos 980, Exynos 1080, E… samsung · exynos_5300_firmware, samsung · exynos_5123_firmware, samsung · exynos_980_firmware +3 2023-04-14 medium6.8 CVE-2023-29086 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor and Modem for Exynos Modem 5123, Exynos Modem 5300, Exynos 980, Exynos 1080, E… samsung · exynos_5300_firmware, samsung · exynos_5123_firmware, samsung · exynos_980_firmware +3 2023-04-14 medium6.8 CVE-2023-29085 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor and Modem for Exynos Modem 5123, Exynos Modem 5300, Exynos 980, Exynos 1080, E… samsung · exynos_5300_firmware, samsung · exynos_5123_firmware, samsung · exynos_980_firmware +3 2023-04-14 medium6.8 CVE-2023-28613 An issue was discovered in Samsung Exynos Mobile Processor and Baseband Modem Processor for Exynos 1280, Exynos 2200, and Exynos Modem 5300. samsung · exynos_1280_firmware, samsung · exynos_2200_firmware, samsung · exynos_modem_5300_firmware 2023-04-04 medium5.5 CVE-2022-33711 Improper validation of integrity check vulnerability in Samsung USB Driver Windows Installer for Mobile Phones prior to version 1.7.56.0 allows local attackers… samsung · android_usb_driver 2022-07-12 medium5.3 CVE-2022-33707 Improper identifier creation logic in Find My Mobile prior to version 7.2.24.12 allows attacker to identify the device. samsung · find_my_mobile 2022-07-12 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 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 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 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 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 medium5.3 CVE-2020-26603 An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) software. google · android 2020-10-06

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.