NetSight

Security Dashboard

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

Reset
2,362 matching advisories · page 15 of 79Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.2 CVE-2024-39674 Plaintext vulnerability in the Gallery search module. huawei · emui, huawei · harmonyos 2024-07-25 medium6.8 CVE-2024-39673 Vulnerability of serialisation/deserialisation mismatch in the iAware module. huawei · emui, huawei · harmonyos 2024-07-25 high8.4 CVE-2024-39672 Memory request logic vulnerability in the memory module. huawei · emui, huawei · harmonyos 2024-07-25 critical9.3 CVE-2024-39671 Access control vulnerability in the security verification module. huawei · emui, huawei · harmonyos 2024-07-25 medium6.2 CVE-2024-39670 Privilege escalation vulnerability in the account synchronisation module. huawei · emui, huawei · harmonyos 2024-07-25 medium5.5 CVE-2023-7271 Privilege escalation vulnerability in the NMS module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-07-25 medium5.5 CVE-2024-40575 An issue in Huawei Technologies opengauss (openGauss 5.0.0 build) v.7.3.0 allows a local attacker to cause a denial of service via the modification of table at… huawei · opengauss 2024-07-24 medium5.9 CVE-2024-5465 Function vulnerabilities in the Calendar module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-06-14 medium4.0 CVE-2024-5464 Vulnerability of insufficient permission verification in the NearLink module Impact: Successful exploitation of this vulnerability may affect service confident… huawei · emui, huawei · harmonyos 2024-06-14 high7.3 CVE-2024-36503 Memory management vulnerability in the Gralloc module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-06-14 high7.9 CVE-2024-36502 Out-of-bounds read vulnerability in the audio module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-06-14 medium5.6 CVE-2024-36501 Memory management vulnerability in the boottime module Impact: Successful exploitation of this vulnerability can affect integrity. huawei · emui, huawei · harmonyos 2024-06-14 high7.8 CVE-2024-36500 Privilege escalation vulnerability in the AMS module Impact: Successful exploitation of this vulnerability may affect service confidentiality. huawei · emui, huawei · harmonyos 2024-06-14 medium6.8 CVE-2024-36499 Vulnerability of unauthorized screenshot capturing in the WMS module Impact: Successful exploitation of this vulnerability may affect service confidentiality. huawei · emui, huawei · harmonyos 2024-06-14 high7.8 CVE-2023-52712 Various Issues Due To Exposed SMI Handler in AmdPspP2CmboxV2. huawei · curiem-wfg9b_firmware 2024-05-28 high7.8 CVE-2023-52711 Various Issues Due To Exposed SMI Handler in AmdPspP2CmboxV2. huawei · curiem-wfg9b_firmware 2024-05-28 high7.8 CVE-2023-52710 Huawei Matebook D16(Model: CREM-WXX9, BIOS: v2.26), As the communication buffer size hasn’t been properly validated to be of the expected size, it can partiall… huawei · curiem-wfg9b_firmware 2024-05-28 high7.8 CVE-2023-52548 Huawei Matebook D16(Model: CREM-WXX9, BIOS: v2.26) Arbitrary Memory Corruption in SMI Handler of ThisiServicesSmm SMM module. huawei · curiem-wfg9b_firmware 2024-05-28 high7.8 CVE-2023-52547 Huawei Matebook D16(Model: CREM-WXX9, BIOS: v2.26. huawei · curiem-wfg9b_firmware 2024-05-28 high7.2 CVE-2022-48681 Some Huawei smart speakers have a memory overflow vulnerability. huawei · egrt-00_firmware 2024-05-28 medium6.4 CVE-2024-4046 Cracking vulnerability in the OS security module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 medium6.8 CVE-2024-32999 Cracking vulnerability in the OS security module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 medium5.9 CVE-2024-32998 NULL pointer access vulnerability in the clock module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 high8.4 CVE-2024-32997 Race condition vulnerability in the binder driver module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 medium6.2 CVE-2024-32996 Privilege escalation vulnerability in the account module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 medium6.2 CVE-2024-32995 Denial of service (DoS) vulnerability in the AMS module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 medium5.6 CVE-2024-32993 Out-of-bounds access vulnerability in the memory module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 high7.5 CVE-2024-32992 Insufficient verification vulnerability in the baseband module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 high7.5 CVE-2024-32991 Permission verification vulnerability in the wpa_supplicant module Impact: Successful exploitation of this vulnerability will affect availability. huawei · emui, huawei · harmonyos 2024-05-14 medium6.1 CVE-2024-32990 Permission 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

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.