# CVE-2020-9059: Denial of service in 500 series

> Attackers can exhaust battery life in Z-Wave devices using S0 authentication, causing locks to fail open and bypass security.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v533-m73v-h37v

## What is CVE-2020-9059?

CVE-2020-9059 is a medium-severity denial of service vulnerability in Schlage 500 series, published on 7 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Z-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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2020-9059?

It affects 2 products.


Products: Schlage Be468, Silabs 500 Series Firmware.

## How do I fix CVE-2020-9059?

No fix has been published for CVE-2020-9059 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-9059 being exploited?

There is no known exploitation of CVE-2020-9059 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9059 and fix it if it is affected.

What it is: CVE-2020-9059 is a medium-severity denial of service vulnerability in Schlage 500 series, published on 7 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-9059 in the wild and no public exploit code.

Affected product: Schlage 500 series. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-9059/ (Markdown: https://insights.sbomify.com/CVE-2020-9059/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-9059
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-9059
- OSV: https://osv.dev/vulnerability/CVE-2020-9059

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-9059/
Summaries are generated and may contain mistakes; the official description above is the record.