dbcve.org
Ex2100e FirmwareOperating system · Ge

CVE-2018-19003

HIGH · 7.5 CVSS v3.0 Published 2018-12-14
Fix available
A fix is available. Upgrade to 04.09.00c or later.
See remediation →
84/100
Remediation priority · High
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
GE Mark VIe, EX2100e, EX2100e_Reg, and LS2100e Versions 03.03.28C to 05.02.04C, EX2100e All versions prior to v04.09.00C, EX2100e_Reg All versions prior to v04.09.00C, and LS2100e All versions prior to v04.09.00C The affected versions of the application have a path traversal vulnerability that fails to restrict the ability of an attacker to gain access to restricted information.

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

A path traversal vulnerability in GE Mark VIe, EX2100e, EX2100e_Reg, and LS2100e control system applications allows remote attackers to access restricted files and information by manipulating file path references (e.g., using ../ sequences). The vulnerability has a CVSS score of 7.5 indicating high severity with network-exploitable remote vector and high confidentiality impact.

MitigationOrganizations should update affected GE control system software to version v04.09.00C or later for EX2100e/EX2100e_Reg/LS2100e series, and beyond version 05.02.04C for Mark VIe. Network segmentation and access controls should be applied as compensating measures until patching is possible.

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
Ex2100e FirmwareOperating system
Affected:< 04.09.00c>= 03.03.28c, <= 05.02.04c
Ls2100e FirmwareOperating system
Affected:< 04.09.00c>= 03.03.28c, <= 05.02.04c
Mark Vle FirmwareOperating system
Affected:>= 03.03.28c, <= 05.02.04c

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the GE control system product model
    Access the controller HMI, system documentation, or management interface to determine if the system is a GE Mark VIe, EX2100e, EX2100e_Reg, or LS2100e controller
    Affected if The product model is one of these four: Mark VIe, EX2100e, EX2100e_Reg, or LS2100e
  2. Determine the installed firmware version
    Log into the controller via its web interface, console, or GE Proficy management tools and navigate to the system information or firmware version section
    Affected if The firmware version is between 03.03.28c and 05.02.04c (inclusive), or for EX2100e/LS2100e specifically, versions below 04.09.00c within that range
  3. Confirm the web server or network file service is enabled
    Check the controller network configuration settings to verify if the embedded web server (EWS) or HTTP-based file access service is active and listening on network ports
    Affected if The web server or any HTTP/HTTPS-based file handling service is enabled and accessible over the network
  4. Verify network accessibility of the file handling interface
    Scan the controller IP address for open HTTP/HTTPS ports (typically ports 80, 443, or custom ports) and attempt to access the file browsing or download endpoints
    Affected if The file access interface is reachable from the network and accepts file path parameters without proper validation

You are affected if you have a GE Mark VIe, EX2100e, EX2100e_Reg, or LS2100e controller running firmware version 03.03.28c through 05.02.04c (or below 04.09.00c for EX2100e/LS2100e) with the web-based file service enabled and 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.

From vendor data
Upgrade available Upgrade to 04.09.00c or later
Fixed in 04.09.00c
Interim mitigation

Organizations should update affected GE control system software to version v04.09.00C or later for EX2100e/EX2100e_Reg/LS2100e series, and beyond version 05.02.04C for Mark VIe. Network segmentation and access controls should be applied as compensating measures until patching is possible.

Fix this in Ex2100e Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-19003 — 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-2018-19003 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