Skip to content
Fencer Intel
high 8.8

CVE-2018-19023 json

Hetronic Nova-M prior to verson r161 uses fixed codes that are reproducible by sniffing and re-transmission.

published 7y ago modified 4mo ago also EUVD-2018-10741

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

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

Patch / fix

  • hetronic nova-m_firmware r161
  • hetronic es-can-hl_firmware main_r1864
  • hetronic bms-hl_firmware main_r1175
  • hetronic mlc_firmware main_r1600
  • hetronic dc_mobile_firmware main_r515

Is CVE-2018-19023 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-19-003-03 updated cvss 7.6

Hetronic Nova-M

  • Hetronic BMS-HL < Main r1175 Estop_v24 Hetronic DC Mobile < Main r515 Estop_v24 Hetronic ES-CAN-HL < Main r1864 Estop_v24 Hetronic MLC < Main r1600 Estop_v24 Hetronic Nova-M < r161
    affected: vendor fix, mitigation “Hetronic recommends that all Nova-M users update their radio transmitters to firmware version r161”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 5.8 AV:A/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Hetronic Hetronic Nova-M

Classification

Weakness
  • CWE-294 Authentication Bypass by Capture-replay
  • CWE-287 Improper Authentication

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.