CVE-2025-9464
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. This vulnerability is triggered during fuzzing of multiple CIP classes, which causes the CIP port to become unresponsive.
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 confidenceA denial-of-service vulnerability exists in ArmorStart® LT motor controllers where fuzzing specific CIP (Common Industrial Protocol) classes causes the CIP port to become unresponsive. The vulnerability is triggered by malformed CIP messages during fuzzing, resulting in service interruption.
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.
-
Confirm ArmorStart LT device on networkIdentify ArmorStart LT motor controllers by checking device inventory, DHCP logs, or network scans for Rockwell Automation ArmorStart LT devices. Note the IP addresses of these devices.Affected if Device is an ArmorStart LT and firmware version is <= 2.002
-
Check installed firmware versionAccess the device web interface or use RSLinx/FactoryTalk Linx to query the device firmware version. Compare against the affected version 2.002.Affected if Firmware version is 2.002 or lower
-
Verify CIP port accessibilityTest connectivity to CIP port (default 44818/TCP) on the ArmorStart LT device using tools like nmap or telnet. Send a valid CIP identity request and observe the response.Affected if CIP port is reachable and responsive to valid CIP messages (indicates service interruption only occurs during fuzzing attack)
-
Review CIP traffic logsCheck network logs, IDS alerts, or the device event log for patterns of malformed CIP messages, especially unusual class IDs or unexpected CIP traffic volumes.Affected if Evidence of malformed CIP traffic targeting the device exists
If the device is an ArmorStart LT with firmware version 2.002 or lower and the CIP port is network-accessible, it is vulnerable to this DoS condition when malformed CIP messages are received.
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 dataImplement network segmentation to isolate the industrial device and restrict CIP traffic to authorized sources using firewall rules or VLANs. Monitor for vendor firmware updates that address the underlying vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9464 — 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-9464 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