# CVE-2018-19983: Denial of service in n/a

> Attackers can cause denial of service on Z-Wave S0 devices by flooding them with split Nonce Get frames, disrupting secure communication.

- **Severity:** Medium 6.5 (`CVSS:3.0/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:** 9 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p576-c9v5-5pvc

## What is CVE-2018-19983?

CVE-2018-19983 is a medium-severity denial of service vulnerability in n/a, published on 9 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on Sigma Design Z-Wave S0 through S2 devices. An attacker first prepares a Z-Wave frame-transmission program (e.g., Z-Wave PC Controller, OpenZWave, CC1110, etc.). Next, the attacker conducts a DoS attack against the Z-Wave S0 Security version product by continuously sending divided "Nonce Get (0x98 0x81)" frames. The reason for dividing the "Nonce Get" frame is that, in security version S0, when a node receives a "Nonce Get" frame, the node produces a random new nonce and sends it to the Src node of the received "Nonce Get" frame. After the nonce value is generated and transmitted, the node transitions to wait mode. At this time, when "Nonce Get" is received again, the node discards the previous nonce value and generates a random nonce again. Therefore, because the frame is encrypted with previous nonce value, the received normal frame cannot be decrypted.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2018-19983?

It affects 2 products.


Products: Silabs Z-Wave S0 Firmware, Silabs Z-Wave S2 Firmware.

## How do I fix CVE-2018-19983?

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

## Is CVE-2018-19983 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19983 and fix it if it is affected.

What it is: CVE-2018-19983 is a medium-severity denial of service vulnerability in n/a, published on 9 Dec 2018. 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-2018-19983 in the wild and no public exploit code.

Affected product: n/a. 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-2018-19983/ (Markdown: https://insights.sbomify.com/CVE-2018-19983/index.md)
```

## Sources

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

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