CVE-2020-9059
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedZ-Wave devices based on Silicon Labs 500 series chipsets using S0 authentication are susceptible to uncontrolled resource consumption leading to battery exhaustion. As an example, the Schlage BE468 version 3.42 door lock is vulnerable and fails open at a low battery level.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceZ-Wave devices using Silicon Labs 500 series chipsets with S0 authentication suffer from an uncontrolled resource consumption vulnerability that causes excessive battery drain. The Schrage BE468 door lock version 3.42 is explicitly affected and can fail open when battery levels drop due to this flaw.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions= 3.42CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Z-Wave device model and firmware versionLocate the device documentation, label, or check the Z-Wave hub/controller interface for the device model and firmware version. For the Schlage Be468, check the model number and firmware version reported by your Z-Wave controller.Affected if The device is a Schlage Be468 with firmware version 3.42, or any Z-Wave device using Silabs 500 Series Firmware regardless of version.
-
Confirm Silicon Labs 500 series chipset is in useCheck the device hardware specifications or product documentation for chipset information. If unknown, consult the manufacturer or check the Silabs website for 500 series product listings.Affected if The device utilizes a Silicon Labs 500 series chipset.
-
Determine Z-Wave security class in useAccess your Z-Wave controller/hub settings and review the security inclusion mode used when the device was paired. Look for S0, S2, or no encryption settings. S0 is the legacy unencrypted mode.Affected if The device is operating with S0 (S0 Legacy) authentication or no security encryption.
-
Monitor for abnormal battery consumptionCheck the Z-Wave controller interface or physically inspect batteries in the device. Compare current battery levels and drain rate against normal expectations for the device type.Affected if Battery levels are depleting unusually fast or dropping below expected life cycles.
You are affected if you have a Schlage Be468 door lock at firmware version 3.42, or any Z-Wave device using Silicon Labs 500 series chipset with S0 authentication enabled, particularly if experiencing unexpected battery drain.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace affected devices with models supporting S2 authentication, or apply manufacturer firmware updates if available to address the battery exhaustion issue.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-9059 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data