NetSight

Security Dashboard

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

Reset
121 matching advisories · page 2 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2024-32989 Insufficient verification vulnerability in the system sharing pop-up module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 low3.5 CVE-2023-52371 Vulnerability of null references in the motor module.Successful exploitation of this vulnerability may affect availability. huawei · emui, huawei · harmonyos 2024-02-18 low3.3 CVE-2023-41310 Keep-alive vulnerability in the sticky broadcast mechanism. huawei · emui, huawei · harmonyos 2023-09-27 low3.7 CVE-2023-41306 Vulnerability of mutex management in the bone voice ID trusted application (TA) module. huawei · emui, huawei · harmonyos 2023-09-27 low3.3 CVE-2023-31225 The Gallery app has the risk of hijacking attacks. huawei · emui 2023-05-26 low3.4 CVE-2022-41603 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41602 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41601 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41600 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41598 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41597 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41595 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41594 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41593 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.4 CVE-2022-41592 The phones have the heap overflow, out-of-bounds read, and null pointer vulnerabilities in the fingerprint trusted application (TA).Successful exploitation of … huawei · emui, huawei · harmonyos 2022-10-14 low3.7 CVE-2021-37073 There is a Race Condition vulnerability in Huawei Smartphone.Successful exploitation of this vulnerability may lead to the detection result is tampered with. huawei · harmonyos 2021-12-07 low3.7 CVE-2021-36994 There is a issue that trustlist strings being repeatedly inserted into the linked list in Huawei Smartphone due to race conditions. huawei · emui, huawei · magic_ui 2021-10-28 low3.3 CVE-2021-22468 A component of the HarmonyOS has a Exposure of Sensitive Information to an Unauthorized Actor vulnerability. huawei · harmonyos 2021-10-28 low3.3 CVE-2021-22464 A component of the HarmonyOS has a Out-of-bounds Read vulnerability. huawei · harmonyos 2021-10-28 low3.3 CVE-2021-22457 A component of the HarmonyOS has a Improper Input Validation vulnerability. huawei · harmonyos 2021-10-28 low3.3 CVE-2021-22453 A component of the HarmonyOS has a Improper Input Validation vulnerability. huawei · harmonyos 2021-10-28 low3.3 CVE-2021-22365 There is an out of bounds read vulnerability in eSE620X vESS V100R001C10SPC200, V100R001C20SPC200, V200R001C00SPC300. huawei · ese620x_vess_firmware 2021-06-22 low3.3 CVE-2021-22308 There is a Business Logic Errors vulnerability in Huawei Smartphone. huawei · emui, huawei · magic_ui 2021-06-03 low3.3 CVE-2021-22294 A component API of the HarmonyOS 2.0 has a permission bypass vulnerability. huawei · harmonyos 2021-03-02 low3.3 CVE-2021-22305 There is a buffer overflow vulnerability in Mate 30 10.1.0.126(C00E125R5P3). huawei · mate_30_firmware 2021-02-06 low3.3 CVE-2021-22304 There is a use after free vulnerability in Taurus-AL00A 10.0.0.1(C00E1R1P1). huawei · taurus-al00a_firmware 2021-02-06 low3.3 CVE-2021-22303 There is a pointer double free vulnerability in Taurus-AL00A 10.0.0.1(C00E1R1P1). huawei · taurus-al00a_firmware 2021-02-06 low3.3 CVE-2020-9203 There is a resource management errors vulnerability in Huawei P30. huawei · p30_firmware 2021-01-13 low2.4 CVE-2020-9083 HUAWEI Mate 20 smart phones with Versions earlier than 10.1.0.163(C00E160R3P8) have a denial of service (DoS) vulnerability. huawei · mate_20_firmware 2020-09-03 low2.4 CVE-2020-9251 HUAWEI Mate 20 smartphones with versions earlier than 10.1.0.160(C00E160R2P11) have an improper authorization vulnerability. huawei · p30_firmware 2020-07-27

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.