Kt Mc01507l Z Wave S0 FirmwareOperating system · Powermanager

CVE-2018-19982

MEDIUM · 5.3 CVSS v3.0 Published 2018-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
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.

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 confidence

Missing HPKP (HTTP Public Key Pinning) implementation in KT MC01507L Z-Wave S0 devices allows Man-in-the-Middle attacks. An attacker on the same network can redirect traffic intended for the Server through a proxy with a fake certificate, enabling cleartext sniffing between Server and Controller, Node control, and Z-Wave network key extraction during pairing mode.

MitigationImplement HPKP or certificate pinning in the device firmware to bind specific certificates/keys to the server, preventing MITM attacks via fake certificates. Additionally, implement mutual TLS authentication between components.

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 data
Kt Mc01507l Z Wave S0 FirmwareOperating system
Affected:all versions

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Locate the physical device or check network inventory for model number 'KT MC01507L' or 'Powermanager' Z-Wave S0 device
    Affected if Device model is KT MC01507L with Z-Wave S0 firmware (all versions are affected)
  2. Check firmware version
    Access the device's web interface or administrative console and locate the firmware version information
    Affected if Any firmware version present on this specific model indicates the vulnerability since all versions are affected
  3. Inspect for HPKP header support
    Send an HTTP request to the device's web interface and examine response headers for 'Public-Key-Pins' or 'Public-Key-Pins-Report-Only' headers
    Affected if Response headers do not contain HPKP headers, confirming the missing protection
  4. Verify certificate pinning configuration
    Check the device settings or configuration files for any certificate pinning or certificate transparency implementation
    Affected if No certificate pinning or HPKP configuration is found on the device

If the device is a KT MC01507L Z-Wave S0 unit with any firmware version and lacks HPKP headers or certificate pinning in its configuration, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement HPKP or certificate pinning in the device firmware to bind specific certificates/keys to the server, preventing MITM attacks via fake certificates. Additionally, implement mutual TLS authentication between components.

Fix this in Kt Mc01507l Z Wave S0 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
84.0 hours of engineering $14,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $23,296.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-19982 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-19982 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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