CVE-2025-8008
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 · uneditedA security issue exists in the protected mode of EN4TR devices, where sending specifically crafted messages during a Forward Close operation can cause the device to crash.
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 · low confidenceA denial-of-service vulnerability exists in EN4TR devices operating in protected mode, where specially crafted messages sent during a Forward Close operation trigger a device crash. This appears to be an input validation or state handling issue specific to the protected mode operation sequence.
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< 7.001< 7.001< 7.001< 7.001< 7.001CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify EN4TR or EN2TR device modelAccess the device web interface, RSLinx configuration, or physical device label to confirm the exact model number (1756-EN2TR or 1756-EN4TR or 1756-EN4TRXT)Affected if The device model is a 1756-EN2TR (any series) or 1756-EN4TR or 1756-EN4TRXT
-
Check firmware versionVia RSLinx Classic or Studio 5000 Logix Designer, navigate to the device properties or use the firmware revision check utility to retrieve the current firmware versionAffected if Firmware version is below 7.001 (for example 6.xxx or any version < 7.001)
-
Confirm protected mode is enabledIn the device web configuration page or RSLinx, inspect the security settings to determine if protected mode operation is currently enabledAffected if Protected mode is enabled on the device
-
Monitor for device crashesCheck system logs, RSLinx connectivity status, or device web interface for unexpected resets, loss of communication, or crash events occurring after Forward Close operationsAffected if Device becomes unresponsive or crashes following Forward Close operations in protected mode
You are affected if you have a 1756-EN2TR or 1756-EN4TR or 1756-EN4TRXT device running firmware below version 7.001 with protected mode enabled, and the device exhibits crashes during Forward Close operations.
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 · scoped7.001
Implement network segmentation to restrict access to EN4TR devices, and apply any vendor-supplied patches when available. Consider disabling protected mode operations if business requirements allow until a fix is deployed.
Firmware version 7.001 or later for 1756-EN2TR Series A/B/C and 1756-EN4TR/EN4TRXT
- Identify the exact series (A, B, or C for EN2TR) and model (EN4TR or EN4TRXT) of the affected device
- Download firmware version 7.001 or later from the Rockwell Automation website or update portal
- Review release notes for any special upgrade requirements or注意事项
- Create a backup of the current device configuration
- Establish a direct console or network connection to the device
- Apply the firmware update following Rockwell Automation's standard firmware upgrade procedures for the 1756-ENxTR series
- After upgrade, verify the device returns to operational state and responds normally
- Confirm the device is running firmware version 7.001 or later using the device management interface
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-8008 — 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-2025-8008 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