Skip to content
Fencer Vulns
low 2.7

CVE-2024-41156 json

Profile files from TRO600 series radios are extracted in plain-text and encrypted file formats.

published 2024-10-29 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-39328

cvss
2.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

Profile files from TRO600 series radios are extracted in plain-text and encrypted file formats. Profile files provide potential attackers valuable configuration information about the Tropos network. Profiles can only be exported by authenticated users with higher privilege of write access.

Patch / fix

  • hitachienergy tro610_firmware 9.2.0.5
  • hitachienergy tro620_firmware 9.2.0.5
  • hitachienergy tro670_firmware 9.2.0.5

Vendor advisories

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

cisa ICSA-24-317-02 updated cvss 2.7

Hitachi Energy TRO600

  • Hitachi Energy TRO600 series firmware versions >=9.0.1.0, <=9.2.0.0
    affected: fixed in 9.2.0.5, mitigation “Hitachi Energy has identified the following specific workarounds and mitigations users can apply to reduce risk:” publisher.hitachienergy.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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Hitachi Energy TRO600

Classification

Weakness
  • CWE-212 Improper Removal of Sensitive Information Before Storage or Transfer

References

Sources

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.