CVE-2018-19023
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 · uneditedHetronic Nova-M prior to verson r161 uses fixed codes that are reproducible by sniffing and re-transmission. This can lead to unauthorized replay of a command, spoofing of an arbitrary message, or keeping the controlled load in a permanent "stop" state.
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 · high confidenceThe Hetronic Nova-M remote control system uses fixed, static transmission codes that can be captured via sniffing and replayed to control the device. This allows attackers to replay commands, spoof arbitrary messages, or lock the controlled load in a permanent 'stop' state.
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< r161< main_r1864< main_r1175< main_r1600< main_r515CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the Hetronic device modelLocate the device label, packaging, or check the management interface for the exact product name (e.g., Nova M, Es Can Hl, Bms Hl, Mlc, or Dc Mobile).Affected if The device is any of the listed Hetronic models.
-
Retrieve the installed firmware versionAccess the device configuration interface, web console, or use the Hetronic programming software to read the current firmware version. The version is typically displayed in system information or about sections.Affected if The firmware version cannot be determined or is below the patched thresholds.
-
Compare firmware version against CVE thresholdsFor Nova M: verify version is r161 or later. For Es Can Hl: verify version is main_r1864 or later. For Bms Hl: verify version is main_r1175 or later. For Mlc: verify version is main_r1600 or later. For Dc Mobile: verify version is main_r515 or later.Affected if The installed version is below these thresholds.
-
Inspect transmission for code variability (optional confirmation)If you have access to RF capture equipment, capture multiple transmission events and examine whether the transmission codes change between each command. Use software-defined radio to intercept and analyze the signal patterns.Affected if The same transmission code is observed across multiple separate command events, indicating static codes are in use.
You are affected if your Hetronic device runs firmware older than the version thresholds listed and uses fixed, static transmission codes that do not change between commands.
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 dataUpdate to version r161 or later which implements proper code randomization or rolling code mechanisms to prevent replay attacks.
- Consultation8.0 h
- Implementation60.0 h
- Testing30.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $31,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19023 — 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-2018-19023 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