# CVE-2018-19982: Security feature bypass in n/a

> Attackers on the local network can intercept cleartext traffic and control smart home devices due to missing HPKP implementation.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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-vcrq-9j44-r9j2

## What is CVE-2018-19982?

CVE-2018-19982 is a medium-severity 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 KT MC01507L Z-Wave S0 devices. It occurs because HPKP is not implemented. The communication architecture is APP > Server > Controller (HUB) > Node (products which are controlled by HUB). The prerequisite is that the attacker is on the same network as the target HUB, and can use IP Changer to change destination IP addresses (of all packets whose destination IP address is Server) to a proxy-server IP address. This allows sniffing of cleartext between Server and Controller. The cleartext command data is transmitted to Controller using the proxy server's fake certificate, and it is able to control each Node of the HUB. Also, by operating HUB in Z-Wave Pairing Mode, it is possible to obtain the Z-Wave network key.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Powermanager Kt Mc01507l Z-Wave S0 Firmware.

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

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

## Is CVE-2018-19982 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19982 is a medium-severity 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-19982 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-19982/ (Markdown: https://insights.sbomify.com/CVE-2018-19982/index.md)
```

## Sources

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

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