CVE-2020-28952

ZigBee traffic disclosure via static test key

Published Mar 9, 2021 · Updated Aug 4, 2024

Hard-coded ZigBee key use in Athom Homey and Homey Pro before 5.0.0 allows physically proximate attackers to decrypt device traffic. The ZigBee hub uses the public test key 01030507090b0d0f00020406080a0c0d as its Standard Network Key instead of generating a unique value, so captured frames can be decrypted. Attackers must be within ZigBee radio range and know the fixed key; the disclosed impact is reading enrolled-device communications, with no reported host compromise.

CVSS severity7.5
High
EPSS probability1.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded ZigBee key use in Athom Homey and Homey Pro before 5.0.0 allows physically proximate attackers to decrypt device traffic. The ZigBee hub uses the public test key 01030507090b0d0f00020406080a0c0d as its Standard Network Key instead of generating a unique value, so captured frames can be decrypted. Attackers must be within ZigBee radio range and know the fixed key; the disclosed impact is reading enrolled-device communications, with no reported host compromise.

The record

CVE
CVE-2020-28952
Published
Mar 9, 2021
Updated
Aug 4, 2024
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-798, T1040
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 9, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
5.0NIST NVDAV:N/AC:L/Au:N/C:P/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-798Use of Hard-coded Credentials
T1040Network Sniffing

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo