Security Advisory

CVE-2018-25029: Z-Wave S2 to S0 Downgrade (Z-Shave)

Last updated:
  • CVE-2018-25029

CVE-2018-25029 is the Z-Shave downgrade: during Z-Wave pairing, an attacker in radio range can strip S2 support from a device's unauthenticated Node Info frame, so the controller pairs it with S0. The weak S0 key exchange then leaks the network key. NVD scores it 8.1 and lists five Silicon Labs Z-Wave modules.

Vulnerability summary

CVSS base score

8.1

High severity

EPSS score (FIRST)

0.6%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2018-25029 · Source: NVD

Affected components

ComponentCPEVersion range
Silicon Labs Z-Wave S2 (specification-level pairing downgrade)—Z-Wave S2, affected per the CERT/CC CVE record; behaviour required by the specification
Silicon Labs Z-Wave modules ZM5101, ZM5202, ZGM130S037HGN, ZGM2305A27HGN and ZGM230SB27HGNcpe:2.3:o:silabs:zm5202_firmware:s2:*:*:*:*:*:*:*Firmware with S2, per the NVD configuration

What does this mean for affected devices?

NVD's description of CVE-2018-25029 reads: "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 pairing to downgrade and then exploit a different vulnerability (CVE-2013-20003) to intercept and spoof traffic." NVD scores it 8.1 (high), vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N; CERT/CC as the CNA gives CWE-757, selection of a less-secure algorithm during negotiation (NVD).

The CVE record was published by CERT/CC on 2022-02-04 and lists Silicon Labs Z-Wave S2 as affected. NVD's configuration names the firmware of five Silicon Labs Z-Wave modules: ZM5101, ZM5202, ZGM130S037HGN, ZGM2305A27HGN and ZGM230SB27HGN. Those are the chip-level parts that device makers build Z-Wave products on.

Pen Test Partners published the attack on 23 May 2018 (Z-Shave write-up). The Node Info frame a device sends when it joins says which command classes it supports, including COMMAND_CLASS_SECURITY_2 (0x9F), and it is "entirely unencrypted and unauthenticated". An attacker who sends a copy without 0x9F makes the controller pair the device with S0. S0 encrypts the network key with a fixed key of zeros, so the attacker then recovers the key and can "intercept and inject S0 traffic on the Z-Wave network". The researchers paired an S2-capable smart lock as S0 this way and could then lock and unlock it. They also found an "S0 downgrade attack" mentioned in Z-Wave documentation and wrote that it "may be a known issue but has not been acknowledged or resolved". The specification says an S2 controller must notify the user when S0 is used.

Because the downgrade is specification behaviour, a firmware patch does not remove it. The controls are the controller warning, the class the controller grants, and where pairing happens. Our Z-Wave protocol security guide covers S2 classes, SmartStart and how to detect a downgraded node. The 2022 CERT/CC disclosure on Silicon Labs chipsets adds the cases with no encryption at all (CVE-2020-9057, CVE-2020-9058).

CVE-2018-25029 is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.00616, percentile 0.501, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).

To reduce the risk, pair devices with S2 Authenticated or S2 Access Control using the DSK PIN or QR code, pair in a controlled location, and treat any S0 result for an S2-capable device as a possible downgrade: exclude the device and include it again. Prefer SmartStart and Z-Wave Long Range where products support it.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • The Z-Wave specification requires that S2 can be downgraded to S0 or less; attacker within radio range during pairing then exploits CVE-2013-20003; NVD Primary CVSS 3.1 8.1 AV:A; CWE-757 (CERT/CC); CPEs zm5101, zm5202, zgm130s037hgn, zgm2305a27hgn, zgm230sb27hgn firmware s2; published 2022-02-04. — NVD
  • CNA certcc; affected vendor Silicon Labs, product Z-Wave, version S2; published 2022-02-04. — CVE record
  • Published 23 May 2018; Node Info entirely unencrypted and unauthenticated; removing class 0x9F forces S0; S0 key encrypted with fixed zero key; specification says S2 controller must notify the user when S0 is used; 'S0 downgrade attack' referenced in Z-Wave documentation. — Pen Test Partners
  • Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.00616 (percentile 0.501), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CVE record (CERT/CC)
  3. Pen Test Partners: Z-Shave. Exploiting Z-Wave downgrade attacks
  4. NVD: CVE-2013-20003
  5. CISA KEV
  6. FIRST EPSS

Frequently asked questions

What is the Z-Shave attack in CVE-2018-25029?

An attacker in radio range during pairing sends a copy of the device's Node Info frame without the S2 command class, so the controller pairs it with S0 and the attacker recovers the network key from S0's weak key exchange (per Pen Test Partners and NVD).

Can a firmware update fix CVE-2018-25029?

Not fully. NVD describes the downgrade as something the Z-Wave specification requires, so the controls are the controller's S0 warning, authenticated S2 inclusion and pairing in a controlled place (per NVD).

Which products are listed for CVE-2018-25029?

The CERT/CC CVE record lists Silicon Labs Z-Wave S2, and NVD's configuration names five Silicon Labs Z-Wave modules: ZM5101, ZM5202, ZGM130S037HGN, ZGM2305A27HGN and ZGM230SB27HGN (per the CVE record and NVD).

Is CVE-2018-25029 in the CISA KEV catalog?

No, not as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.00616 in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).