CVE-2018-14827
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 · uneditedRockwell Automation RSLinx Classic Versions 4.00.01 and prior. A remote, unauthenticated threat actor may intentionally send specially crafted Ethernet/IP packets to Port 44818, causing the software application to stop responding and crash. The user must restart the software to regain functionality.
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 confidenceRSLinx Classic versions 4.00.01 and prior are vulnerable to a remote denial-of-service condition. An unauthenticated attacker can send specially crafted Ethernet/IP packets to Port 44818, causing the application to stop responding and crash, requiring a manual restart to restore functionality.
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<= 4.00.01CVSS 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.
-
Verify RSLinx Classic is installedCheck for RSLinx Classic installation by looking in the Windows Start Menu under 'Rockwell Software' or by checking the installation directory (typically C:\Program Files\Rockwell Software\RSLinx\) for RSLinx.exeAffected if RSLinx Classic executable is present on the system
-
Determine installed RSLinx versionRight-click on RSLinx.exe, select Properties, then go to the Details tab to view the File Version. Alternatively, open RSLinx Classic and go to Help > About RSLinx Classic to see the version numberAffected if The displayed version is 4.00.01 or lower
-
Check if RSLinx service is runningOpen Windows Services (services.msc), locate the RSLinx service, and verify its status. Or run 'sc query RSLinx' from an elevated command promptAffected if The RSLinx service is in a Running state
-
Verify port 44818 is listeningOpen Command Prompt and run 'netstat -an | findstr 44818' to check if port 44818 is in LISTENING state. This indicates the service is accepting Ethernet/IP connectionsAffected if Port 44818 shows as LISTENING or ESTABLISHED, meaning the service is exposed on the network
You are affected if RSLinx Classic version 4.00.01 or lower is installed AND the service is running with port 44818 accessible on the network.
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 dataUpgrade RSLinx Classic to a version newer than 4.00.01. If immediate patching is not feasible, implement network segmentation or firewall rules to restrict unauthorized access to Port 44818 from untrusted networks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14827 — 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-14827 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