NetSight

Security Dashboard

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

Reset
308 matching advisories · page 10 of 11Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2023-20841 In imgsys, 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-20840 In imgsys, there is a possible out of bounds read and write due to a missing valid range checking. linuxfoundation · yocto, mediatek · iot_yocto, google · android +1 2023-09-04 medium4.2 CVE-2023-20839 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 medium6.4 CVE-2023-20835 In camsys, there is a possible use after free due to a race condition. linuxfoundation · yocto, mediatek · iot_yocto, google · android 2023-09-04 medium4.4 CVE-2023-20812 In wlan driver, there is a possible out of bounds write due to improper input validation. mediatek · iot_yocto, google · android 2023-08-07 medium6.7 CVE-2023-20673 In vcu, there is a possible memory corruption due to type confusion. mediatek · iot_yocto, google · android 2023-05-15 medium5.5 CVE-2023-23001 In the Linux kernel before 5.16.3, drivers/scsi/ufs/ufs-mediatek.c misinterprets the regulator_get return value (expects it to be NULL in the error case, where… linux · linux_kernel 2023-03-01 medium6.7 CVE-2022-32656 In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. mediatek · mt5221_firmware, mediatek · mt7603_firmware, mediatek · mt7613_firmware +9 2023-02-06 medium6.7 CVE-2022-32655 In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. mediatek · mt5221_firmware, mediatek · mt7603_firmware, mediatek · mt7613_firmware +9 2023-02-06 medium6.7 CVE-2022-32654 In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. mediatek · mt5221_firmware, mediatek · mt7603_firmware, mediatek · mt7613_firmware +9 2023-02-06 medium6.7 CVE-2022-32659 In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. mediatek · mt7603_firmware, thelinuxfoundation · yocto, mediatek · mt7613_firmware +9 2023-01-03 medium6.7 CVE-2022-32658 In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. mediatek · mt7603_firmware, mediatek · mt7613_firmware, mediatek · mt7615_firmware +7 2023-01-03 medium6.7 CVE-2022-32657 In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. mediatek · mt7603_firmware, mediatek · mt7613_firmware, mediatek · mt7615_firmware +7 2023-01-03 medium6.7 CVE-2022-26445 In wifi driver, there is a possible out of bounds write due to a missing bounds check. mediatek · mt7603_firmware, mediatek · mt7610_firmware, mediatek · mt7612_firmware +9 2022-08-01 medium6.7 CVE-2022-26444 In wifi driver, there is a possible out of bounds write due to a missing bounds check. mediatek · mt7603_firmware, mediatek · mt7610_firmware, mediatek · mt7612_firmware +9 2022-08-01 medium6.7 CVE-2022-26443 In wifi driver, there is a possible out of bounds write due to a missing bounds check. mediatek · mt7603_firmware, mediatek · mt7610_firmware, mediatek · mt7612_firmware +9 2022-08-01 medium6.7 CVE-2022-26442 In wifi driver, there is a possible out of bounds write due to a missing bounds check. mediatek · mt7603_firmware, mediatek · mt7610_firmware, mediatek · mt7612_firmware +9 2022-08-01 medium6.7 CVE-2022-26441 In wifi driver, there is a possible out of bounds write due to a missing bounds check. mediatek · mt7603_firmware, mediatek · mt7610_firmware, mediatek · mt7612_firmware +9 2022-08-01 medium6.7 CVE-2022-26440 In wifi driver, there is a possible out of bounds write due to a missing bounds check. mediatek · mt7603_firmware, mediatek · mt7610_firmware, mediatek · mt7612_firmware +9 2022-08-01 medium6.7 CVE-2022-26439 In wifi driver, there is a possible out of bounds write due to a missing bounds check. mediatek · mt7603_firmware, mediatek · mt7610_firmware, mediatek · mt7612_firmware +9 2022-08-01 medium6.7 CVE-2022-26438 In wifi driver, there is a possible out of bounds write due to a missing bounds check. mediatek · mt7603_firmware, mediatek · mt7610_firmware, mediatek · mt7612_firmware +9 2022-08-01 medium6.5 CVE-2021-41789 In wifi driver, there is a possible system crash due to a missing validation check. mediatek · mt7615_firmware, mediatek · mt7622_firmware 2022-01-04 medium6.5 CVE-2021-41788 MediaTek microchips, as used in NETGEAR devices through 2021-12-13 and other devices, mishandle attempts at Wi-Fi authentication flooding. mediatek · mt7603e_firmware, mediatek · mt7612_firmware, mediatek · mt7613_firmware +5 2021-12-26 medium4.4 CVE-2021-25477 An improper error handling in Mediatek RRC Protocol stack prior to SMR Oct-2021 Release 1 allows modem crash and remote denial of service. google · android 2021-10-06 medium5.4 CVE-2019-18989 A partial authentication bypass vulnerability exists on Mediatek MT7620N 1.06 devices. mediatek · mt7620n_firmware 2020-09-30 medium6.8 CVE-2020-25280 An issue was discovered on Samsung mobile devices with Q(10.0) (Exynos and MediaTek chipsets) software. google · android 2020-09-11 medium6.7 CVE-2020-12465 An array overflow was discovered in mt76_add_fragment in drivers/net/wireless/mediatek/mt76/dma.c in the Linux kernel before 5.5.10, aka CID-b102f0c522cf. linux · linux_kernel, netapp · active_iq_unified_manager, netapp · cloud_backup +6 2020-04-29 medium5.5 CVE-2017-0625 An information disclosure vulnerability in the MediaTek command queue driver could enable a local malicious application to access data outside of its permissio… google · android 2017-05-12 medium4.7 CVE-2017-0532 An information disclosure vulnerability in the MediaTek video codec driver could enable a local malicious application to access data outside of its permission … google · android 2017-03-08 medium5.5 CVE-2017-0529 An information disclosure vulnerability in the MediaTek driver could enable a local malicious application to access data outside of its permission levels. google · android 2017-03-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.