First published: Tue Mar 09 2021(Updated: )
An issue was discovered on Athom Homey and Homey Pro devices before 5.0.0. ZigBee hub devices should generate a unique Standard Network Key that is then exchanged with all enrolled devices so that all inter-device communication is encrypted. However, the cited Athom products use another widely known key that is designed for testing purposes: "01030507090b0d0f00020406080a0c0d" (the decimal equivalent of 1 3 5 7 9 11 13 15 0 2 4 6 8 10 12 13), which is human generated and static across all issued devices.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Homey | <5.0.0 | |
Homey Homey Pro | ||
Homey | <5.0.0 | |
Homey |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-28952 is classified as a medium severity vulnerability due to its potential exposure to unauthorized access.
The fix for CVE-2020-28952 involves upgrading the firmware of the affected Athom Homey and Homey Pro devices to version 5.0.0 or later.
CVE-2020-28952 affects Athom Homey and Homey Pro devices that are running firmware versions prior to 5.0.0.
CVE-2020-28952 can be exploited to allow unauthorized access to encrypted inter-device communication through the use of known Standard Network Keys.
Yes, CVE-2020-28952 is specifically related to weaknesses in the ZigBee network encryption due to use of a static network key.