CVE-2020-25159
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 · unedited499ES EtherNet/IP (ENIP) Adaptor Source Code is vulnerable to a stack-based buffer overflow, which may allow an attacker to send a specially crafted packet that may result in a denial-of-service condition or code execution.
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 confidenceThe 499ES EtherNet/IP adaptor contains a stack-based buffer overflow vulnerability in its packet processing code. An attacker can send specially crafted ENIP packets that overflow a fixed-size stack buffer during parsing, allowing denial of service or potentially arbitrary code execution on the device.
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< 2.28CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Confirm the 499ES EtherNet/IP adaptor is present in your environmentIdentify any RTA Automation 499ES Ethernet/IP adaptor devices on your network through network scanning, asset inventory, or physical inspection of deployed equipmentAffected if The device is present and processing ENIP traffic on the network
-
Determine the installed firmware versionAccess the device web interface, check the device console/SSH login for firmware version display, or query the device via ENIP get attribute requests if supportedAffected if The firmware version cannot be determined or is confirmed to be below 2.28
-
Verify ENIP packet processing is enabledCheck device configuration through its web interface or management console to confirm EtherNet/IP protocol handling is actively enabledAffected if ENIP protocol processing is enabled and the device is accepting incoming ENIP traffic
-
Review network exposure of the deviceExamine network segmentation, firewall rules, and access controls to determine if the device is directly accessible from untrusted networksAffected if The device is accessible from network segments outside of its expected operational zone
-
Inspect for indicators of exploitationReview network logs, IDS/IPS alerts, or device event logs for signs of malformed ENIP packet attempts, device crashes, or unexpected behaviorAffected if Any evidence of malformed ENIP packets or device instability is observed
You are affected if an RTA Automation 499ES EtherNet/IP adaptor with firmware version below 2.28 is present and has ENIP packet processing enabled on an accessible network segment.
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.
dbcve · scoped2.28
Apply vendor patches if available; otherwise, implement network segmentation to isolate the device and deploy IDS/IPS rules to detect and block malformed ENIP packets targeting this vulnerability.
Firmware version 2.28 or later
- Identify the current firmware version of the 499ES EtherNet/IP Adaptor by accessing the device management interface or checking system documentation
- Obtain the firmware version 2.28 or later from the device vendor (refer to us-cert.cisa.gov or the official vendor support channels for the download location)
- Follow the vendor's standard firmware update procedure, typically involving uploading the firmware file through the device's web interface, console, or management software
- After applying the update, verify that the firmware has been successfully upgraded to version 2.28 or later
- Confirm that the device is functioning normally and that the vulnerability has been remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25159 — 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-25159 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