Gate E1 FirmwareOperating system · Abb

CVE-2018-18997

MEDIUM · 6.1 CVSS v3.0 Published 2019-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Pluto Safety PLC Gateway Ethernet devices in ABB GATE-E1 and GATE-E2 all versions allows an unauthenticated attacker using the administrative web interface to insert an HTML/Javascript payload into any of the device properties, which may allow an attacker to display/execute the payload in a visitor browser.

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

Stored cross-site scripting (XSS) vulnerability in the administrative web interface of ABB GATE-E1 and GATE-E2 Pluto Safety PLC Gateway devices allows unauthenticated attackers to inject malicious HTML/JavaScript code into device properties, which executes when viewed by legitimate users.

MitigationImplement network segmentation to isolate the device from untrusted networks, restrict web interface access to trusted IPs only, and consider disabling the administrative web interface if not required for operations.

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
Gate E1 FirmwareOperating system
Affected:all versions
Gate E2 FirmwareOperating system
Affected:all versions

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 ABB GATE-E1 or GATE-E2 devices on the network
    Scan the network for devices with vendor identifier ABB and product names GATE-E1 or GATE-E2. Check network inventory records or use Nmap with service detection: nmap -sV --script=banner target IP ranges
    Affected if Any GATE-E1 or GATE-E2 device is found on the network
  2. Confirm the administrative web interface is enabled
    Attempt to access the device web interface via HTTP/HTTPS on common ports 80, 443, 8080. Check if the login page or device status page loads for the GATE-E1/E2
    Affected if The web interface is accessible and responds with ABB GATE-E device pages
  3. Check device firmware version
    Log into the web interface or check device documentation/backup configs for the firmware version field. If accessible via CLI, use command 'show version' or similar
    Affected if Firmware version information shows any version - all versions are affected
  4. Inspect device properties for injected scripts
    In the web interface, navigate to device properties or configuration pages. Look for any fields containing HTML tags (<script>, <iframe>, onload=, onerror=) or unusual JavaScript code that does not match expected configuration
    Affected if Any device property field contains unexpected HTML, JavaScript code, or suspicious encoded content
  5. Review web server logs for XSS attack patterns
    If device logging is accessible, review logs for GET/POST requests containing patterns like <script>, javascript:, or HTML tags in parameter values sent to the device
    Affected if Logs show requests with XSS payloads targeting device configuration parameters

You are affected if any ABB GATE-E1 or GATE-E2 device with an accessible administrative web interface is present in your environment, since all firmware versions are vulnerable to stored XSS.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement network segmentation to isolate the device from untrusted networks, restrict web interface access to trusted IPs only, and consider disabling the administrative web interface if not required for operations.

Fix this in Gate E1 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2018-18997 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