NetSight

Security Dashboard

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

Reset
308 matching advisories · page 9 of 11Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2023-52873 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data Add the check for the return va… linux · linux_kernel 2024-05-21 medium4.1 CVE-2023-52870 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6765: Add check for mtk_alloc_clk_data Add the check for the return va… linux · linux_kernel 2024-05-21 medium5.5 CVE-2023-52865 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6797: Add check for mtk_alloc_clk_data Add the check for the return va… linux · linux_kernel 2024-05-21 medium6.2 CVE-2023-52858 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt7629: Add check for mtk_alloc_clk_data Add the check for the return va… linux · linux_kernel 2024-05-21 medium5.5 CVE-2023-52857 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix coverity issue with unintentional integer overflow 1. linux · linux_kernel 2024-05-21 medium5.5 CVE-2024-35842 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: sof-common: Add NULL check for normal_link string It's not granted that all… linux · linux_kernel 2024-05-17 medium5.5 CVE-2024-27068 In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/mediatek/lvts_thermal: Fix a memory leak in an error handling path If devm_… linux · linux_kernel 2024-05-01 medium5.5 CVE-2024-27002 In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: Do a runtime PM get on controllers during probe mt8183-mfgcfg has a mutual d… linux · linux_kernel 2024-05-01 medium4.7 CVE-2023-52645 In the Linux kernel, the following vulnerability has been resolved: pmdomain: mediatek: fix race conditions with genpd If the power domains are registered firs… linux · linux_kernel 2024-04-17 medium4.7 CVE-2024-26874 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip It's possible that … linux · linux_kernel, debian · debian_linux 2024-04-17 medium6.3 CVE-2024-20055 In imgsys, there is a possible information disclosure due to a missing bounds check. linuxfoundation · yocto, mediatek · iot_yocto, google · android 2024-04-01 medium5.5 CVE-2021-47108 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: hdmi: Perform NULL pointer check for mtk_hdmi_conf In commit 41ca9caaae0b ("d… linux · linux_kernel 2024-03-04 medium5.9 CVE-2024-20019 In wlan driver, there is a possible memory leak due to improper input handling. mediatek · software_package 2024-03-04 medium6.7 CVE-2023-32891 In bluetooth service, there is a possible out of bounds write due to improper input validation. google · android, mediatek · lr13, mediatek · nr15 +2 2024-01-02 medium5.5 CVE-2023-32831 In wlan driver, there is a possible PIN crack due to use of insufficiently random values. mediatek · software_development_kit 2024-01-02 medium6.5 CVE-2023-32840 In modem CCCI, there is a possible out of bounds write due to a missing bounds check. mediatek · lr12a, mediatek · nr15, mediatek · nr16 +1 2023-11-06 medium6.7 CVE-2023-32829 In apusys, there is a possible out of bounds write due to an integer overflow. linuxfoundation · yocto, mediatek · iot_yocto, google · android 2023-10-02 medium6.7 CVE-2023-32828 In vpu, there is a possible out of bounds write due to an integer overflow. mediatek · iot_yocto, google · android 2023-10-02 medium6.7 CVE-2023-32811 In connectivity system driver, there is a possible out of bounds write due to improper input validation. linuxfoundation · yocto, mediatek · iot_yocto, google · android 2023-09-04 medium4.4 CVE-2023-32807 In wlan service, there is a possible out of bounds read due to improper input validation. linuxfoundation · yocto, mediatek · iot_yocto, google · android 2023-09-04 medium6.7 CVE-2023-32806 In wlan driver, there is a possible out of bounds write due to improper input validation. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium6.5 CVE-2023-20850 In imgsys_cmdq, there is a possible out of bounds write due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium6.5 CVE-2023-20849 In imgsys_cmdq, there is a possible use after free due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium6.5 CVE-2023-20848 In imgsys_cmdq, there is a possible out of bounds read due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium4.2 CVE-2023-20847 In imgsys_cmdq, there is a possible out of bounds read due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium4.2 CVE-2023-20846 In imgsys_cmdq, there is a possible out of bounds read due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium4.2 CVE-2023-20845 In imgsys, there is a possible out of bounds read due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium4.2 CVE-2023-20844 In imgsys_cmdq, there is a possible out of bounds read due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium4.2 CVE-2023-20843 In imgsys_cmdq, there is a possible out of bounds read due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium6.5 CVE-2023-20842 In imgsys_cmdq, there is a possible out of bounds write due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-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.