NetSight

Security Dashboard

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

Reset
237 matching advisories · page 4 of 8Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.7 CVE-2024-27385 A vulnerability was discovered in the slsi_handle_nan_rx_event_log_ind function in Samsung Mobile Processor Exynos 1380 and Exynos 1480 related to no input val… samsung · exynos_1380_firmware, samsung · exynos_1480_firmware 2024-07-09 medium5.3 CVE-2024-28068 A vulnerability was discovered in SS in Samsung Mobile Processor, Wearable Processor, and Modems with versions Exynos 9820, Exynos 9825, Exynos 980, Exynos 990… samsung · exynos_9820_firmware, samsung · exynos_9825_firmware, samsung · exynos_980_firmware +9 2024-07-09 medium6.0 CVE-2024-27363 A vulnerability was discovered in Samsung Mobile Processor Exynos 850, Exynos 9610, Exynos 980, Exynos 1280, Exynos 1380, Exynos 1330, Exynos W920, and Exynos … 2024-07-09 medium5.1 CVE-2024-27361 A vulnerability was discovered in Samsung Mobile Processor Exynos 980, Exynos 990, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, Exynos 1380, and Exynos … samsung · exynos_980_firmware, samsung · exynos_990_firmware, samsung · exynos_1080_firmware +5 2024-07-09 medium6.2 CVE-2024-31957 A vulnerability was discovered in Samsung Mobile Processors Exynos 2200 and Exynos 2400 where they lack a check for the validation of native handles, which can… samsung · exynos_2200_firmware, samsung · exynos_2400_firmware 2024-07-09 medium4.4 CVE-2024-27362 A vulnerability was discovered in Samsung Mobile Processors Exynos 1280, Exynos 2200, Exynos 1330, Exynos 1380, and Exynos 2400 where they do not properly chec… samsung · exynos_1280_firmware, samsung · exynos_2200_firmware, samsung · exynos_1330_firmware +2 2024-07-09 medium6.0 CVE-2024-27360 A vulnerability was discovered in Samsung Mobile Processors Exynos 850, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, Exynos 1380, Exynos 1330, and Exyno… samsung · exynos_850_firmware, samsung · exynos_1080_firmware, samsung · exynos_2100_firmware +5 2024-07-09 medium6.8 CVE-2024-31958 An issue was discovered in Samsung Mobile Processor EExynos 2200, Exynos 1480, Exynos 2400. samsung · exynos_2200_firmware, samsung · exynos_1480_firmware, samsung · exynos_2400_firmware 2024-06-07 medium5.9 CVE-2024-28818 An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, Exynos 990, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, … samsung · exynos_980_firmware, samsung · exynos_990_firmware, samsung · exynos_1080_firmware +8 2024-06-05 medium6.0 CVE-2024-27382 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.0 CVE-2024-27381 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.0 CVE-2024-27380 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27379 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.0 CVE-2024-27378 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27377 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27376 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27375 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27374 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27373 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27372 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27371 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium6.7 CVE-2024-27370 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +2 2024-06-05 medium5.3 CVE-2023-49927 An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, Exynos 990, Exynos 850, Exynos 1080, Exynos 2100, Exynos 2200, E… samsung · exynos_9820_firmware, samsung · exynos_9825_firmware, samsung · exynos_980_firmware +9 2024-06-05 medium5.9 CVE-2024-29152 An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, Exynos 990, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, … samsung · exynos_980_firmware, samsung · exynos_990_firmware, samsung · exynos_850_firmware +9 2024-06-04 medium4.0 CVE-2023-45864 A race condition issue discovered in Samsung Mobile Processor Exynos 9820, 980, 1080, 2100, 2200, 1280, and 1380 allows unintended modifications of values with… samsung · exynos_9820_firmware, samsung · exynos_980_firmware, samsung · exynos_1080_firmware +4 2023-12-13 medium4.8 CVE-2023-43122 Samsung Mobile Processor and Wearable Processor (Exynos 980, 850, 1080, 2100, 2200, 1280, 1380, 1330, and W920) allow Information Disclosure in the Bootloader. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1080_firmware +6 2023-12-13 medium6.3 CVE-2023-42483 A TOCTOU race condition in Samsung Mobile Processor Exynos 9820, Exynos 980, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, and Exynos 1380 can cause unex… samsung · exynos_9820_firmware, samsung · exynos_980_firmware, samsung · exynos_1080_firmware +4 2023-12-13 medium4.7 CVE-2023-41911 Samsung Mobile Processor Exynos 2200 allows a GPU Double Free (issue 1 of 2). samsung · exynos_2200_firmware 2023-09-28 medium4.7 CVE-2023-42482 Samsung Mobile Processor Exynos 2200 allows a GPU Use After Free. samsung · exynos_2200_firmware 2023-09-21 medium5.9 CVE-2023-37368 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor, and Modem (Exynos Mobile Processor, Automotive Processor, and Modem - Exynos … samsung · exynos_9810_firmware, samsung · exynos_9610_firmware, samsung · exynos_9820_firmware +9 2023-09-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.