CVE-2025-9283
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 within ArmorStart® LT that can result in a denial-of-service condition. During execution of the Achilles EtherNet/IP Step Limits Storms tests, the device reboots unexpectedly, causing the Link State Monitor to go down for several seconds.
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 ArmorStart® LT motor starter experiences unexpected reboots when subjected to Achilles EtherNet/IP Step Limits Storms test traffic, causing the Link State Monitor to go down for several seconds. This represents a denial-of-service vulnerability exploitable via crafted network packets on the EtherNet/IP protocol.
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.002CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/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 ArmorStart LT devices on the networkUse network scanning tools or industrial protocol discovery (such as Rockwell's RSLinx, Rockwell's Network Diagnostics, or third-party EtherNet/IP scanners) to enumerate devices. Look for devices reporting vendor ID for Rockwell Automation and product name containing 'ArmorStart LT' or similar identifiers.Affected if An ArmorStart LT device is found responding on the network.
-
Determine the installed firmware versionAccess the device through its web interface, Rockwell's RSLogix/Studio 5000 environment, or RSLinx Classic. Navigate to the device properties or firmware revision information. Alternatively, query the device via EtherNet/IP CIP object 0x01 (Identity Object) to retrieve the revision fields.Affected if The firmware version is 2.002 or lower.
-
Verify EtherNet/IP protocol is enabledCheck the device configuration through its web interface or PLC programming software. Confirm that EtherNet/IP communication is actively configured and the device is participating in EtherNet/IP I/O or messaging.Affected if EtherNet/IP is enabled and the device is actively communicating on an EtherNet/IP network.
-
Assess network accessibility of the deviceReview network segmentation, firewall rules, and VLAN configurations surrounding the ArmorStart LT device. Determine if the device is directly accessible from untrusted network segments or the internet.Affected if The device is accessible from untrusted networks without firewall or segmentation protection.
A user is affected if they have an ArmorStart LT device with firmware version 2.002 or lower that has EtherNet/IP enabled and is exposed to untrusted network traffic capable of sending crafted EtherNet/IP packets.
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 dataIsolate ArmorStart® LT devices behind firewalls or network segmentation to limit exposure to untrusted network traffic. Contact Rockwell Automation for potential firmware updates addressing this vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9283 — 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-9283 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