CVE-2019-10955
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 Rockwell Automation MicroLogix 1400 Controllers Series A, All Versions Series B, v15.002 and earlier, MicroLogix 1100 Controllers v14.00 and earlier, CompactLogix 5370 L1 controllers v30.014 and earlier, CompactLogix 5370 L2 controllers v30.014 and earlier, CompactLogix 5370 L3 controllers (includes CompactLogix GuardLogix controllers) v30.014 and earlier, an open redirect vulnerability could allow a remote unauthenticated attacker to input a malicious link to redirect users to a malicious site that could run or download arbitrary malware on the user’s machine.
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 confidenceAn open redirect vulnerability exists in the web interface of Rockwell Automation MicroLogix 1400, MicroLogix 1100, and CompactLogix 5370 controllers. An unauthenticated remote attacker can craft malicious URLs containing arbitrary redirect targets, tricking legitimate users into visiting attacker-controlled websites where malware can be downloaded onto the user's machine.
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 dataall versions<= 15.002<= 14.00<= 30.014<= 30.014<= 30.014CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the controller modelAccess the device web interface or check network documentation to determine if the device is a MicroLogix 1400, MicroLogix 1100, or CompactLogix 5370. The model is typically displayed on the web login page or can be queried via RSLinx.Affected if The device is a MicroLogix 1400, MicroLogix 1100, or CompactLogix 5370 controller.
-
Check the firmware versionLog into the device web interface and navigate to the Device Status or About page to view the firmware version. For MicroLogix 1400, verify if it is Series A (any version), Series B (version 15.002 or lower), or Series B (version 15.003 or higher). For MicroLogix 1100, check if version is 14.00 or lower. For CompactLogix 5370 L1/L2/L3, check if version is 30.014 or lower.Affected if Firmware version is MicroLogix 1400 Series A (any), MicroLogix 1400 Series B <= 15.002, MicroLogix 1100 <= 14.00, or CompactLogix 5370 any L1/L2/L3 <= 30.014.
-
Verify the web interface is enabledConfirm that the device web server is running by attempting to access the device IP address in a web browser. Check the device configuration via RSLinx or the web interface settings to confirm HTTP/HTTPS web server is enabled.Affected if The web interface is enabled and accessible over the network.
-
Test for open redirect behavior (optional)If the web interface is accessible, attempt to access a URL such as http://[device_ip]/redirect.asp?url=http://example.com to observe if the device performs an external redirect. A vulnerable device will redirect to the arbitrary URL, while a patched device will either block the request or redirect to an internal page.Affected if The device redirects to an external arbitrary URL when provided in the redirect parameter.
You are affected if your device is a MicroLogix 1400 (any Series A, Series B <= 15.002), MicroLogix 1100 <= 14.00, or CompactLogix 5370 L1/L2/L3 <= 30.014, AND the web interface is enabled and accessible.
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 dataUpdate affected controllers to patched firmware versions: MicroLogix 1400 Series B to v15.003 or later, MicroLogix 1100 to v14.01 or later, and CompactLogix 5370 L1/L2/L3 to v30.015 or later. If patching is not immediately feasible, disable the web interface or implement network segmentation to restrict access to trusted networks only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10955 — 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-2019-10955 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