NetSight

Security Dashboard

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

Reset
2,362 matching advisories · page 18 of 79Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2023-52363 Vulnerability of defects introduced in the design process in the Control Panel module.Successful exploitation of this vulnerability may cause app processes to … huawei · emui, huawei · harmonyos 2024-02-18 high7.5 CVE-2023-52362 Permission management vulnerability in the lock screen module.Successful exploitation of this vulnerability may affect availability. huawei · emui, huawei · harmonyos 2024-02-18 high7.5 CVE-2023-52361 The VerifiedBoot module has a vulnerability that may cause authentication errors.Successful exploitation of this vulnerability may affect integrity. huawei · harmonyos 2024-02-18 high7.5 CVE-2023-52360 Logic vulnerabilities in the baseband.Successful exploitation of this vulnerability may affect service integrity. huawei · emui, huawei · harmonyos 2024-02-18 medium6.2 CVE-2023-52358 Vulnerability of configuration defects in some APIs of the audio module.Successful exploitation of this vulnerability may affect availability. huawei · emui, huawei · harmonyos 2024-02-18 high7.5 CVE-2023-52357 Vulnerability of serialization/deserialization mismatch in the vibration framework.Successful exploitation of this vulnerability may affect availability. huawei · emui, huawei · harmonyos 2024-02-18 high7.5 CVE-2023-52097 Vulnerability of foreground service restrictions being bypassed in the NMS module.Successful exploitation of this vulnerability may affect service confidential… huawei · emui, huawei · harmonyos 2024-02-18 medium4.4 CVE-2023-52106 Vulnerability of permission verification for APIs in the DownloadProviderMain module. huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52105 The nearby module has a privilege escalation vulnerability. huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52104 Vulnerability of parameters being not verified in the WMS module. huawei · emui, huawei · harmonyos 2024-01-16 critical9.8 CVE-2023-52103 Buffer overflow vulnerability in the FLP module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52102 Vulnerability of parameters being not verified in the WMS module. huawei · emui, huawei · harmonyos 2024-01-16 critical9.1 CVE-2023-52101 Component exposure vulnerability in the Wi-Fi module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52100 The Celia Keyboard module has a vulnerability in access control. huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52099 Vulnerability of foreground service restrictions being bypassed in the NMS module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52116 Permission management vulnerability in the multi-screen interaction module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52115 The iaware module has a Use-After-Free (UAF) vulnerability. huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52114 Data confidentiality vulnerability in the ScreenReader module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52108 Vulnerability of process priorities being raised in the ActivityManagerService module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52107 Vulnerability of permissions being not strictly verified in the WMS module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52098 Denial of Service (DoS) vulnerability in the DMS module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52113 launchAnyWhere vulnerability in the ActivityManagerService module. huawei · emui, huawei · harmonyos 2024-01-16 medium5.3 CVE-2023-52112 Unauthorized file access vulnerability in the wallpaper service module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52111 Authorization vulnerability in the BootLoader module. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52110 The sensor module has an out-of-bounds access vulnerability.Successful exploitation of this vulnerability may affect availability. huawei · harmonyos 2024-01-16 high7.5 CVE-2023-52109 Vulnerability of trust relationships being inaccurate in distributed scenarios. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-4566 Vulnerability of trust relationships being inaccurate in distributed scenarios. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-44117 Vulnerability of trust relationships being inaccurate in distributed scenarios. huawei · emui, huawei · harmonyos 2024-01-16 high7.5 CVE-2023-44112 Out-of-bounds access vulnerability in the device authentication module. huawei · emui, huawei · harmonyos 2024-01-16 medium6.4 CVE-2022-48616 A Huawei data communication product has a command injection vulnerability. huawei · ar617vw_firmware 2023-12-12

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.