CVE-2020-14504
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 mishandles authentication for HTTP POST requests. A remote, unauthenticated attacker can send a crafted request that may allow for modification of the configuration settings.
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 communication module's web interface fails to properly enforce authentication for HTTP POST requests, allowing remote unauthenticated attackers to send crafted requests that can modify device configuration settings. This is an authentication bypass specific to POST request handling.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 modelLocate the 1734-AENTR module in your asset inventory or physically inspect the device label to confirm it is a Point I/O Dual Port Network Adaptor. Note whether it is Series B or Series C.Affected if The device is not a 1734-AENTR unit.
-
Determine the firmware versionAccess the device's web interface or use the vendor's management software (such as RSLogix/Connected Components Workbench) to retrieve the installed firmware version. Consult the device documentation for the specific command or menu path to display firmware information.Affected if The firmware version falls within the affected ranges: Series B >= 4.001 to <= 4.005, or >= 5.011 to <= 5.017; Series C = 6.011 or 6.012.
-
Confirm the web interface is enabledCheck the device configuration settings to determine if the embedded web server or HTTP interface is enabled. This is typically found in the network or web server settings section of the device web UI or management tool.Affected if The web interface is enabled and accessible over the network.
-
Verify network accessibility of the web serviceDetermine whether the device HTTP port (default 80/443 or vendor-assigned) is reachable from network segments that contain untrusted or external systems. Use network scanning or review firewall rules to confirm exposure.Affected if The device web interface is reachable from network segments outside the trusted control system network.
The device is affected if it is a 1734-AENTR Series B or C running an affected firmware version AND the web interface is enabled and 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 dataApply vendor firmware updates if available; otherwise, network-segment the device behind a firewall, disable the web interface if not operationally required, or implement compensating access controls to restrict unauthorized configuration changes.
- Consultation8.0 h
- Implementation4.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14504 — 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-14504 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