NetSight

Security Dashboard

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

Reset
105 matching advisories · page 4 of 4Index updated 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2022-24611 Denial of Service (DoS) in the Z-Wave S0 NonceGet protocol specification in Silicon Labs Z-Wave 500 series allows local attackers to block S0/S2 protected Z-Wa… silabs · zm5202_firmware, silabs · zm5101_firmware, silabs · sd3503_firmware +2 2022-05-17 medium6.5 CVE-2021-27411 Micrium OS Versions 5.10.1 and prior are vulnerable to integer wrap-around in functions Mem_DynPoolCreate, Mem_DynPoolCreateHW and Mem_PoolCreate. silabs · micrium_os 2022-05-03 high8.1 CVE-2018-25029 The Z-Wave specification requires that S2 security can be downgraded to S0 or other less secure protocols, allowing an attacker within radio range during pairi… silabs · zgm130s037hgn_firmware, silabs · zm5202_firmware, silabs · zm5101_firmware +2 2022-02-04 high8.3 CVE-2013-20003 Z-Wave devices from Sierra Designs (circa 2013) and Silicon Labs (using S0 security) may use a known, shared network key of all zeros, allowing an attacker wit… silabs · zgm130s037hgn_firmware, silabs · zm5202_firmware, silabs · zm5101_firmware +2 2022-02-04 medium6.5 CVE-2020-9061 Z-Wave devices using Silicon Labs 500 and 700 series chipsets, including but not likely limited to the SiLabs UZB-7 version 7.00, ZooZ ZST10 version 6.04, Aeon… aeotec · zw090-a, samsung · sth-eth-200, silabs · uzb-7 +3 2022-01-10 medium6.5 CVE-2020-9060 Z-Wave devices based on Silicon Labs 500 series chipsets using S2, including but likely not limited to the ZooZ ZST10 version 6.04, ZooZ ZEN20 version 5.03, Zo… silabs · 500_series_firmware, aeotec · zw090-a, fibaro · fgwpb-111 +3 2022-01-10 medium6.5 CVE-2020-9059 Z-Wave devices based on Silicon Labs 500 series chipsets using S0 authentication are susceptible to uncontrolled resource consumption leading to battery exhaus… silabs · 500_series_firmware, schlage · be468 2022-01-10 high8.1 CVE-2020-9058 Z-Wave devices based on Silicon Labs 500 series chipsets using CRC-16 encapsulation, including but likely not limited to the Linear LB60Z-1 version 3.5, Dome D… silabs · 500_series_firmware, dome · dm501, jasco · zw4201 +1 2022-01-10 high8.8 CVE-2020-9057 Z-Wave devices based on Silicon Labs 100, 200, and 300 series chipsets do not support encryption, allowing an attacker within radio range to take control of or… linear · wadwaz-1, linear · wapirz-1, silabs · 100_series_firmware +2 2022-01-10 medium6.5 CVE-2020-10137 Z-Wave devices based on Silicon Labs 700 series chipsets using S2 do not adequately authenticate or encrypt FIND_NODE_IN_RANGE frames, allowing a remote, unaut… silabs · uzb-7, silabs · 700_series_firmware 2022-01-10 medium6.5 CVE-2021-31609 The Bluetooth Classic implementation in Silicon Labs iWRAP 6.3.0 and earlier does not properly handle the reception of an oversized LMP packet greater than 17 … silabs · iwrap 2021-09-07 high7.5 CVE-2020-13582 A denial-of-service vulnerability exists in the HTTP Server functionality of Micrium uC-HTTP 3.01.00. silabs · micrium_uc-http 2021-01-26 medium6.5 CVE-2020-15532 Silicon Labs Bluetooth Low Energy SDK before 2.13.3 has a buffer overflow via packet data. silabs · bluetooth_low_energy_software_development_kit 2020-08-20 high8.8 CVE-2020-15531 Silicon Labs Bluetooth Low Energy SDK before 2.13.3 has a buffer overflow via packet data. silabs · bluetooth_low_energy_software_development_kit 2020-08-20 medium6.5 CVE-2018-19983 An issue was discovered on Sigma Design Z-Wave S0 through S2 devices. silabs · z-wave_s0_firmware, silabs · z-wave_s2_firmware 2018-12-09

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.