NetSight

Security Dashboard

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

Reset
604 matching advisories · page 12 of 21Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2024-20148 In wlan STA FW, there is a possible out of bounds write due to improper input validation. linuxfoundation · yocto, mediatek · software_development_kit, google · android 2025-01-06 high8.1 CVE-2024-20146 In wlan STA driver, there is a possible out of bounds write due to improper input validation. linuxfoundation · yocto, mediatek · software_development_kit, google · android +1 2025-01-06 medium5.5 CVE-2024-56685 In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: Check num_codecs is not zero to avoid panic during probe Following commit 1… linux · linux_kernel 2024-12-28 medium5.5 CVE-2024-53238 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtk: adjust the position to init iso data anchor MediaTek iso data anchor init… linux · linux_kernel 2024-12-27 medium6.7 CVE-2018-9391 In update_gps_sv and output_vzw_debug of vendor/mediatek/proprietary/hardware/connectivity/gps/gps_hal/src/gpshal_wor ker.c, there is a possible out of bounds … google · android 2024-12-05 medium6.7 CVE-2018-9400 In gt1x_debug_write_proc and gt1x_tool_write of drivers/input/touchscreen/mediatek/GT1151/gt1x_generic.c and gt1x_tools.c, there is a possible out of bounds wr… google · android 2024-12-05 medium6.7 CVE-2018-9398 In fm_set_stat of mediatek FM radio driver, there is a possible OOB write due to improper input validation. google · android 2024-12-05 medium6.7 CVE-2018-9396 In rpc_msg_handler and related handlers of drivers/misc/mediatek/eccci/port_rpc.c, there is a possible out of bounds write due to an incorrect bounds check. google · android 2024-12-04 medium6.7 CVE-2018-9395 In mtk_cfg80211_vendor_packet_keep_alive_start and mtk_cfg80211_vendor_set_config of drivers/misc/mediatek/connectivity/wlan/gen2/os/linux/gl_vendor.c, there i… google · android 2024-12-04 medium6.7 CVE-2018-9394 In mtk_p2p_wext_set_key of drivers/misc/mediatek/connectivity/wlan/gen2/os/linux/gl_p2p.c, there is a possible OOB write due to improper input validation. google · android 2024-12-04 medium6.7 CVE-2018-9393 In procfile_write of drivers/misc/mediatek/connectivity/wlan/gen2/os/linux/gl_proc.c, there is a possible OOB write due to a missing bounds check. google · android 2024-12-04 medium6.7 CVE-2018-9392 In get_binary of vendor/mediatek/proprietary/hardware/connectivity/gps/gps_hal/src/data_coder.c, there is a possible out of bounds write due to a missing bound… google · android 2024-12-04 medium6.7 CVE-2018-9376 In rpc_msg_handler and related handlers of drivers/misc/mediatek/eccci/port_rpc.c, there is a possible out of bounds write due to an incorrect bounds check. google · android 2024-12-02 medium6.5 CVE-2024-20139 In Bluetooth firmware, there is a possible firmware asssert due to improper handling of exceptional conditions. linuxfoundation · yocto, mediatek · software_development_kit, google · android +1 2024-12-02 high7.5 CVE-2024-20138 In wlan driver, there is a possible out of bound read due to improper input validation. mediatek · software_development_kit, google · android 2024-12-02 medium6.7 CVE-2024-20133 In Modem, there is a possible escalation of privilege due to an incorrect bounds check. mediatek · nr16 2024-12-02 medium6.7 CVE-2024-20132 In Modem, there is a possible out of bonds write due to a mission bounds check. mediatek · nr16 2024-12-02 medium6.7 CVE-2024-20131 In Modem, there is a possible escalation of privilege due to an incorrect bounds check. mediatek · nr16, mediatek · nr17 2024-12-02 medium6.4 CVE-2018-9371 In the Mediatek Preloader, there are out of bounds reads and writes due to an exposed interface that allows arbitrary peripheral memory mapping with insufficie… google · android 2024-11-19 medium5.5 CVE-2024-53056 In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy() In mtk_crtc_create(), if… linux · linux_kernel 2024-11-19 medium5.5 CVE-2024-47754 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Fix H264 multi stateless decoder smatch warning Fix a smatch stati… linux · linux_kernel 2024-10-21 medium5.5 CVE-2024-47753 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Fix VP8 stateless decoder smatch warning Fix a smatch static check… linux · linux_kernel 2024-10-21 medium5.5 CVE-2024-47752 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Fix H264 stateless decoder smatch warning Fix a smatch static chec… linux · linux_kernel 2024-10-21 critical9.8 CVE-2024-20103 In wlan firmware, there is a possible out of bounds write due to improper input validation. mediatek · software_development_kit, google · android 2024-10-07 critical9.8 CVE-2024-20101 In wlan driver, there is a possible out of bounds write due to improper input validation. mediatek · software_development_kit, google · android 2024-10-07 critical9.8 CVE-2024-20100 In wlan driver, there is a possible out of bounds write due to improper input validation. mediatek · iot_yocto, mediatek · software_development_kit, google · android 2024-10-07 high7.5 CVE-2024-20094 In Modem, there is a possible system crash due to a missing bounds check. mediatek · nr15 2024-10-07 medium5.5 CVE-2024-43831 In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Handle invalid decoder vsi Handle an invalid decoder vsi in vpu_de… linux · linux_kernel 2024-08-17 medium5.5 CVE-2024-42282 In the Linux kernel, the following vulnerability has been resolved: net: mediatek: Fix potential NULL pointer dereference in dummy net_device handling Move the… linux · linux_kernel 2024-08-17 critical9.8 CVE-2024-20082 In Modem, there is a possible memory corruption due to a missing bounds check. mediatek · nr15, mediatek · nr16, mediatek · nr17 2024-08-14

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.