CVE-2025-9279
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 Limit Storm 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 · high confidenceThe ArmorStart® LT motor controller contains a denial-of-service vulnerability where processing of specific EtherNet/IP Step Limit Storm test packets causes an unexpected device reboot, resulting in the Link State Monitor being unavailable for several seconds.
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 device on networkLocate ArmorStart LT motor controllers by reviewing network documentation, device inventories, or using industrial protocol scanners to identify EtherNet/IP devices with vendor ID 0x0b (Allen-Bradley/Rockwell) and product name containing 'ArmorStart' or 'ArmorStart LT'Affected if The device is an ArmorStart LT motor controller on the network
-
Check firmware versionAccess the device web interface, use RSLinx Classic or FactoryTalk View to connect to the device and retrieve the firmware version, or query the device via EtherNet/IP CIP object 0x01 (Identity Object) to read the product name and revision fieldsAffected if Firmware version is 2.002 or lower
-
Verify EtherNet/IP protocol is enabledCheck device network configuration to confirm EtherNet/IP communication is enabled. Review device configuration files or use CIP protocol analyzer to capture EtherNet/IP traffic destined to the deviceAffected if EtherNet/IP protocol is enabled and accepting traffic
-
Check network exposureReview firewall rules, VLAN assignments, and network segmentation to determine if the device is directly accessible from untrusted networks. Identify any external or flat network connections that could allow malicious EtherNet/IP packets to reach the deviceAffected if Device is accessible from networks beyond the isolated industrial control system segment
A user is affected if they have an ArmorStart LT device running firmware version 2.002 or lower with EtherNet/IP enabled and accessible to potential attackers sending malicious Step Limit Storm test 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 dataApply vendor-supplied firmware updates when available; in the interim, isolate the device behind a firewall or network segmentation to limit exposure to malicious EtherNet/IP traffic, and implement rate limiting on industrial protocol traffic.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9279 — 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-9279 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