dbcve.org
Relion 670 FirmwareOperating system · Hitachienergy

CVE-2019-18253

CRITICAL · 10.0 CVSS v3.1 Published 2019-11-27
Fix available
A fix is available. Upgrade to 1.2.3.17 / 1p1r26 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a path traversal vulnerability in the Relion 670 Series protection relay web interface. An attacker can use specially crafted paths in HTTP requests to escape the intended directory and read or delete arbitrary files on the device, potentially exposing configuration data, credentials, or causing denial of service.

MitigationApply vendor-supplied firmware updates for affected versions (1p1r26, 1.2.3.17, 2.0.0.10, RES670 2.0.0.4, 2.1.0.1 and prior). If patching is not immediately possible, restrict network access to the web interface via firewall rules or network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Relion 670 FirmwareOperating system
Affected:< 1p1r26>= 1.2, < 1.2.3.17>= 2.0, < 2.0.0.10>= 2.1, < 2.1.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Relion 670 firmware version
    Log into the web interface and navigate to the Device Info, About, or System Status page to view the firmware version. Alternatively, access the device via CLI and use the command to display firmware version (typically 'firmware version' or 'show version').
    Affected if The displayed firmware version matches any of the affected ranges: < 1p1r26; >= 1.2 and < 1.2.3.17; >= 2.0 and < 2.0.0.10; >= 2.1 and < 2.1.0.1
  2. Confirm the web interface is enabled
    Attempt to access the device web interface via HTTP/HTTPS on the typical web port (typically 80 or 443). If the login page or web portal responds, the web interface is active.
    Affected if The web interface is accessible and responds to HTTP/HTTPS requests, making the path traversal flaw exploitable over the network
  3. Check network exposure of the web interface
    Identify the IP address assigned to the Relion 670 device and determine if it is reachable from untrusted networks. Use network scanning tools or review firewall configurations to map exposure.
    Affected if The device web interface is reachable from external or untrusted network segments without adequate access controls

The environment is affected if the Relion 670 firmware version falls within any of the vulnerable ranges AND the web interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.3.17 / 1p1r26 / 2.0.0.10 or later
Fixed in 1.2.3.171p1r262.0.0.10
Interim mitigation

Apply vendor-supplied firmware updates for affected versions (1p1r26, 1.2.3.17, 2.0.0.10, RES670 2.0.0.4, 2.1.0.1 and prior). If patching is not immediately possible, restrict network access to the web interface via firewall rules or network segmentation to limit exposure.

Recommended fix High confidence

Upgrade to firmware 1p1r26 (for 1p1 branch), 1.2.3.17 (for 1.2.x branch), 2.0.0.10 (for 2.0.x branch), or 2.1.0.1 (for 2.1.x branch) depending on your current branch

  1. Identify the current firmware version of the Relion 670 device by accessing the device management interface or checking the system documentation
  2. Determine which firmware branch the device is currently running (1p1, 1.2.x, 2.0.x, or 2.1.x)
  3. Download the appropriate fixed firmware version from the official ABB Relion product support page or authorized distribution channel
  4. Review the firmware upgrade instructions in the Relion 670 installation and commissioning manual
  5. Follow the vendor's recommended procedure to upload and install the new firmware version
  6. After upgrading, verify the firmware version has been correctly applied and test that the device functions normally
  7. Validate that the path traversal vulnerability is no longer exploitable by confirming proper access controls are enforced
Caveat Review ABB Relion 670 release notes for the specific version to check for any configuration or feature changes that may require adaptation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Relion 670 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18253 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-18253 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data