CVE-2020-14502
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 · uneditedThe web interface of the 1734-AENTR communication module is vulnerable to stored XSS. A remote, unauthenticated attacker could store a malicious script within the web interface that, when executed, could modify some string values on the homepage of the web interface.
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 confidenceThe 1734-AENTR EtherNet/IP communication module's web interface contains a stored cross-site scripting vulnerability. An unauthenticated remote attacker can inject malicious JavaScript into the web interface, which persists and executes when users access the homepage, allowing modification of string values displayed on that page.
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.001, <= 4.005>= 5.011, <= 5.017= 6.011= 6.012CVSS 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 device modelAccess the device web interface or use network discovery to confirm the device is a 1734-AENTR Point I/O Dual Port Network Adaptor. Check the device homepage or SNMP sysDescr for the model identifier.Affected if The device is not a 1734-AENTR series (Series B or C).
-
Check the firmware versionLog into the device web interface and navigate to the System Information or Device Status page to view the firmware version. Alternatively, use the device's built-in web server or API to query the firmware version.Affected if The firmware version falls within Series B: >= 4.001 through <= 4.005 OR >= 5.011 through <= 5.017, OR Series C: = 6.011 OR = 6.012.
-
Verify if the web interface is enabledAttempt to access the device's web interface via HTTP/HTTPS on the standard web ports. Confirm that the web pages load and are reachable.Affected if The web interface is accessible and the firmware version is within the affected ranges listed above.
-
Inspect the homepage for injected scriptsView the source code of the device homepage and look for any script tags, event handlers, or suspicious JavaScript that was not part of the default firmware. Check any displayed string values for encoded or obfuscated XSS payloads.Affected if Unexpected JavaScript code or modified string values are present in the homepage HTML source.
The user is affected if they have a 1734-AENTR Series B or C device with an affected firmware version (as listed above) and the web interface is accessible, with potential evidence of injected scripts on the homepage.
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 available vendor firmware updates from Rockwell Automation. If no update is available, implement network segmentation to restrict access to the device's web interface and deploy WAF rules to detect and block XSS payloads.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14502 — 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-2020-14502 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