CVE-2019-18253
CVE-2019-18253 is a critical-severity vulnerability in Hitachienergy Relion 670 Firmware with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.
Key facts
- Severity: Critical (CVSS 3.x base score 10.0)
- CVSS v2: 7.5
- EPSS exploit prediction: 2% (81st percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-22
- Affected product: Hitachienergy Relion 670 Firmware
- Published:
- Last modified:
Description
An attacker could use specially crafted paths in a specific request to read or delete files from Relion 670 Series (versions 1p1r26, 1.2.3.17, 2.0.0.10, RES670 2.0.0.4, 2.1.0.1, and prior) outside the intended directory.
Frequently asked questions
- What is CVE-2019-18253?
- An attacker could use specially crafted paths in a specific request to read or delete files from Relion 670 Series (versions 1p1r26, 1.2.3.17, 2.0.0.10, RES670 2.0.0.4, 2.1.0.1, and prior) outside the intended directory.
- How severe is CVE-2019-18253?
- CVE-2019-18253 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2019-18253 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2019-18253?
- CVE-2019-18253 affects Hitachienergy Relion 670 Firmware. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2019-18253?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2019-18253 published?
- CVE-2019-18253 was published on 2019-11-27 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:o:hitachienergy:relion_670_firmware:*:*:*:*:*:*:*:*
More vulnerabilities in Hitachienergy Relion 670 Firmware
- CVE-2021-35535 — High (CVSS 8.1): Insecure Boot Image vulnerability in Hitachi Energy Relion Relion 670/650/SAM600-IO series allows an attacker who…
- CVE-2021-27196 — High (CVSS 7.5): Improper Input Validation vulnerability in Hitachi ABB Power Grids Relion 670 Series, Relion 670/650 Series, Relion…
- CVE-2019-18247 — High (CVSS 7.5): An attacker may use a specially crafted message to force Relion 650 series (versions 1.3.0.5 and prior) or Relion 670…
- CVE-2021-35534 — High (CVSS 7.2): Insufficient security control vulnerability in internal database access mechanism of Hitachi Energy Relion…
- CVE-2023-4518 — Medium (CVSS 6.5): A vulnerability exists in the input validation of the GOOSE messages where out of range values received and processed…
- CVE-2022-3353 — Medium (CVSS 5.9): A vulnerability exists in the IEC 61850 communication stack that affects multiple Hitachi Energy products. An…
All CVEs affecting Hitachienergy Relion 670 Firmware →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-77312 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429…
- CVE-2026-121351 — Critical (CVSS 10.0): Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')…
- CVE-2026-121489 — Critical (CVSS 10.0): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau. The…
- CVE-2026-122013 — Critical (CVSS 10.0): A vulnerability was detected in Comfast CF-WR632AX 2.6.0.1. Affected by this vulnerability is an unknown functionality…
- CVE-2026-61738 — Critical (CVSS 10.0): SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to…
- CVE-2026-112690 — Critical (CVSS 10.0): This issue was addressed with improved input validation. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2…