A vulnerability exists in the input validation of the GOOSE messages where out of range values received and processed by the IED caused a
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.70% (FIRST EPSS); higher than 52.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability exists in the input validation of the GOOSE messages where out of range values received and processed by the IED caused a reboot of the device. In order for an attacker to exploit the vulnerability, goose receiving blocks need to be configured.
- Published
- Dec 1, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 52th percentile
- CWE
- CWE-1284
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- 7.5
- CNA · Hitachi Energy
- 6.5
- 1.0 point gap
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hitachienergy | relion 670 firmware | cpe:2.3:o:hitachienergy:relion_670_firmware |
| hitachienergy | relion 670 | cpe:2.3:h:hitachienergy:relion_670 |
| hitachienergy | relion 650 firmware | cpe:2.3:o:hitachienergy:relion_650_firmware |
| hitachienergy | relion 650 | cpe:2.3:h:hitachienergy:relion_650 |
| hitachienergy | relion sam600-io firmware | cpe:2.3:o:hitachienergy:relion_sam600-io_firmware |
| hitachienergy | relion sam600-io | cpe:2.3:h:hitachienergy:relion_sam600-io |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hitachienergy relion 650 firmware2.2.4 and later · before 2.2.4.4
- hitachienergy relion 650 firmware2.2.5 and later · before 2.2.5.6
- hitachienergy relion 650 firmware2.2.1
- hitachienergy relion 650 firmware2.2.1.6
- hitachienergy relion 670 firmware2.2.0 and later · before 2.2.2.6
- hitachienergy relion 670 firmware2.2.3 and later · before 2.2.3.7
- hitachienergy relion 670 firmware2.2.4 and later · before 2.2.4.4
- hitachienergy relion 670 firmware2.2.5 and later · before 2.2.5.6
- hitachienergy relion sam600-io firmware2.2.5 and later · before 2.2.5.6
- hitachienergy relion sam600-io firmware2.2.1
- hitachienergy relion sam600-io firmware2.2.1.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Hitachi Energy). Independent of NVD's CPE analysis and usually ahead of it.
Hitachi Energy Relion670
- Relion 670 series version 2.2.0 all revisions, Relion 670/650/SAM600-IO series version 2.2.1 all revisions, elion 670 series version 2.2.2 all revisions, Relion 670 series version 2.2.3 all revisions, Relion 670/650 series version 2.2.4 all revisions, Relion 670/650/SAM600-IO series version 2.2.5 all revisionsaffected
Same product
hitachienergy: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-18253An attacker could use specially crafted paths in a specific request to read or delete files from Relion 670 Series (versions 1p1r26, 1.2.3.141Plan
- CVE-2021-35535Insufficient Security Control Vulnerability32Monitor
- CVE-2021-27196Specially Crafted IEC 61850 Protocol Sequence Vulnerability30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1284 · Improper Validation of Specified Quantity in InputCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.