# CVE-2018-19023: Security feature bypass in Hetronic Nova-M

> Attackers can replay commands or spoof messages in Hetronic Nova-M devices due to fixed codes, potentially causing unauthorized control or denial of service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 25 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rfmh-rwpf-wvmp

## What is CVE-2018-19023?

CVE-2018-19023 is a high-severity vulnerability in Hetronic Nova-M, published on 25 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication), CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 5 products.


Products: Hetronic Bms-Hl Firmware, Hetronic Dc Mobile Firmware, Hetronic Es-Can-Hl Firmware, Hetronic Mlc Firmware, Hetronic Nova-M Firmware.

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

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

## Is CVE-2018-19023 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19023 is a high-severity vulnerability in Hetronic Nova-M, published on 25 Jan 2019. 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-19023 in the wild and no public exploit code.

Affected product: Hetronic Nova-M. 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-19023/ (Markdown: https://insights.sbomify.com/CVE-2018-19023/index.md)
```

## Sources

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

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