CVE-2018-8867
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 · uneditedIn GE PACSystems RX3i CPE305/310 version 9.20 and prior, RX3i CPE330 version 9.21 and prior, RX3i CPE 400 version 9.30 and prior, PACSystems RSTi-EP CPE 100 all versions, and PACSystems CPU320/CRU320 RXi all versions, the device does not properly validate input, which could allow a remote attacker to send specially crafted packets causing the device to become unavailable.
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 · moderate confidenceThis is an input validation vulnerability in GE PACSystems RX3i and RSTi-EP PLCs. A remote attacker can send specially crafted packets to the device that exploit improper input validation, causing the device to become unavailable (denial of service). The vulnerability affects multiple CPE models and CPU320/CRU320 variants across different firmware versions.
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<= 9.20<= 9.20<= 9.21<= 9.30all versionsall versionsall versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the exact PLC modelLocate the physical PLC hardware or check your asset inventory to determine if the device is one of: RX3i CPE305, CPE310, CPE330, CPE400, RSTi-EP CPE100, CPU320, CRU320, or RXI. Consult the device labeling or management interface for the model number.Affected if The device is any of the listed models (CPE305, CPE310, CPE330, CPE400, CPE100, CPU320, CRU320, or RXI).
-
Determine the installed firmware versionAccess the PLC through its management interface, Proficy programming software, or system documentation to retrieve the current firmware version. Compare this version against the affected version ranges.Affected if For CPE305/CPE310: firmware is 9.20 or lower. For CPE330: firmware is 9.21 or lower. For CPE400: firmware is 9.30 or lower. For CPE100, CPU320, CRU320, or RXI: any firmware version (all versions affected).
-
Verify network accessibilityReview network segmentation, firewall rules, and access controls to determine if the PLC is reachable from untrusted networks. This vulnerability is exploitable remotely via network packets.Affected if The PLC is directly accessible from corporate networks, the internet, or any untrusted network segment without firewall filtering.
You are affected if your device is a GE PACSystems RX3i or RSTi-EP PLC (any of the listed models) and it is running a firmware version within the affected ranges or is accessible over a network where an attacker could send malicious packets.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-provided firmware updates: upgrade RX3i CPE305/310 to version 9.30 or later, CPE330 to version 9.40 or later, and CPE400 to version 9.40 or later; contact GE for patches for RSTi-EP CPE100 and CPU320/CRU320 (all versions). Implement network segmentation and firewalls to limit attack surface as a compensating control until patches are applied.
- Consultation12.0 h
- Implementation20.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8867 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-8867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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