NetSight

Security Dashboard

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

Reset
4,692 matching advisories · page 36 of 157Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.2 CVE-2024-34662 Improper access control in ActivityManager prior to SMR Oct-2024 Release 1 in select Android 12, 13 and SMR Sep-2024 Release 1 in select Android 14 allows loca… samsung · android 2024-10-08 high8.1 CVE-2024-44068 An issue was discovered in the m2m scaler driver in Samsung Mobile Processor and Wearable Processor Exynos 9820, 9825, 980, 990, 850,and W920. samsung · exynos_9820_firmware, samsung · exynos_9825_firmware, samsung · exynos_980_firmware +3 2024-10-07 high7.1 CVE-2024-43971 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in sunshinephotocart Sunshine Photo Cart sunshine-photo-cart… sunshinephotocart · sunshine_photo_cart 2024-09-18 high7.8 CVE-2024-5760 The Samsung Universal Print Driver for Windows is potentially vulnerable to escalation of privilege allowing the creation of a reverse shell in the tool. samsung · universal_print_driver 2024-09-11 medium6.5 CVE-2024-45407 Sunshine is a self-hosted game stream host for Moonlight. lizardbyte · sunshine 2024-09-10 high7.8 CVE-2024-31960 An issue was discovered in Samsung Mobile Processor Exynos 1480, Exynos 2400. samsung · exynos_1480_firmware, samsung · exynos_2400_firmware 2024-09-10 medium5.9 CVE-2024-25074 An issue was discovered in Samsung Semiconductor Mobile Processor and Modem Exynos 9820, Exynos 9825, Exynos 980, Exynos 990, Exynos 850, Exynos 1080, Exynos 2… samsung · exynos_9820_firmware, samsung · exynos_9825_firmware, samsung · exynos_980_firmware +9 2024-09-10 medium5.9 CVE-2024-25073 An issue was discovered in Samsung Semiconductor Mobile Processor and Modem Exynos 9820, Exynos 9825, Exynos 980, Exynos 990, Exynos 850, Exynos 1080, Exynos 2… samsung · exynos_1080_firmware, samsung · exynos_1280_firmware, samsung · exynos_1330_firmware +9 2024-09-10 critical9.8 CVE-2024-40754 Heap-based Buffer Overflow vulnerability in Samsung Open Source Escargot JavaScript engine allows Overflow Buffers.This issue affects Escargot: 4.0.0. 2024-09-10 medium4.4 CVE-2024-27365 An issue was discovered in Samsung Mobile Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920… samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1080_firmware +6 2024-09-09 medium6.7 CVE-2024-27387 An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. samsung · exynos_1080_firmware, samsung · exynos_1280_firmware, samsung · exynos_1330_firmware +6 2024-09-09 medium6.7 CVE-2024-27383 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_1080_firmware +6 2024-09-09 medium4.4 CVE-2024-27368 An issue was discovered in Samsung Mobile Processor Exynos Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, … samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1080_firmware +6 2024-09-09 medium4.4 CVE-2024-27367 An issue was discovered in Samsung Mobile Processor Exynos Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exyno… samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1080_firmware +6 2024-09-09 medium4.4 CVE-2024-27366 An issue was discovered in Samsung Mobile Processor, Wearable Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exyn… samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1080_firmware +6 2024-09-09 medium4.4 CVE-2024-27364 An issue was discovered in Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos… samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1080_firmware +6 2024-09-09 medium4.3 CVE-2024-34661 Improper handling of insufficient permissions in Samsung Assistant prior to version 9.1.00.7 allows remote attackers to access location data. samsung · assistant 2024-09-04 high7.3 CVE-2024-34660 Heap-based out-of-bounds write in Samsung Notes prior to version 4.4.21.62 allows local attackers to execute arbitrary code. samsung · notes 2024-09-04 high7.5 CVE-2024-34659 Exposure of sensitive information in GroupSharing prior to version 13.6.13.3 allows remote attackers can force the victim to join the group. samsung · group_sharing 2024-09-04 medium4.0 CVE-2024-34658 Out-of-bounds read in Samsung Notes allows local attackers to bypass ASLR. samsung · notes 2024-09-04 high8.6 CVE-2024-34657 Stack-based out-of-bounds write in Samsung Notes prior to version 4.4.21.62 allows remote attackers to execute arbitrary code. samsung · notes 2024-09-04 high7.3 CVE-2024-34656 Path traversal in Samsung Notes prior to version 4.4.21.62 allows local attackers to execute arbitrary code. samsung · notes 2024-09-04 medium6.2 CVE-2024-34655 Incorrect use of privileged API in UniversalCredentialManager prior to SMR Sep-2024 Release 1 allows local attackers to access privileged API related to Univer… samsung · android 2024-09-04 medium6.2 CVE-2024-34654 Improper Export of android application component in My Files prior to SMR Sep-2024 Release 1 allows local attackers to access files with My Files' privilege. samsung · android 2024-09-04 medium4.6 CVE-2024-34653 Path Traversal in My Files prior to SMR Sep-2024 Release 1 allows physical attackers to access directories with My Files' privilege. samsung · android 2024-09-04 medium4.0 CVE-2024-34652 Incorrect authorization in kperfmon prior to SMR Sep-2024 Release 1 allows local attackers to access information related to performance including app usage. samsung · android 2024-09-04 medium6.2 CVE-2024-34651 Improper authorization in My Files prior to SMR Sep-2024 Release 1 allows local attackers to access restricted data in My Files. samsung · android 2024-09-04 medium4.0 CVE-2024-34650 Incorrect authorization in CocktailbarService prior to SMR Sep-2024 Release 1 allows local attackers to access privileged APIs related to Edge panel. samsung · android 2024-09-04 low2.4 CVE-2024-34649 Improper access control in new Dex Mode in multitasking framework prior to SMR Sep-2024 Release 1 allows physical attackers to temporarily access an unlocked s… samsung · android 2024-09-04 medium5.1 CVE-2024-34648 Improper Handling of Insufficient Permissions in KnoxMiscPolicy prior to SMR Sep-2024 Release 1 allows local attackers to access sensitive data. samsung · android 2024-09-04

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.