CVE-2016-2294 json
The AXM-NET module in Accuenergy Acuvim II NET Firmware 3.08 and Acuvim IIR NET Firmware 3.08 allows remote attackers to discover a clearte…
published 2016-04-21 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-3378
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
The AXM-NET module in Accuenergy Acuvim II NET Firmware 3.08 and Acuvim IIR NET Firmware 3.08 allows remote attackers to discover a cleartext mail-server password via unspecified vectors.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-16-105-02 updated cvss 7.5
Accuenergy Acuvim II Series AXM-NET Module Vulnerabilities
-
Accuenergy Acuvim II NET Firmware 3.08 Accuenergy Acuvim IIR NET Firmware 3.08affected: mitigation “Accuenergy has produced a document containing recommended mitigations. It is available at: (https://www.accuenergy.com/page/articles/protecting-your-modbus-tcp-ip-meter-from-security-risks)” accuenergy.com
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
1.52% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
ics-cert.us-cert.gov
/advisories/ICSA-16-105-02
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2016-2294
- NVD CVE-2016-2294
Fencer Vulns 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.