Rockwell Automation ArmorStart AOP denial-of-service flaw
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Uncaught exception in ArmorStart AOP allows remote denial-of-service; no patch available.
Rockwell Automation's ArmorStart AOP (Add-On Profile) for Studio 5000 Logix Designer contains an uncaught exception vulnerability in its COM method input handling affecting version V2.05.07 and earlier. The flaw allows unauthenticated remote attackers with low attack complexity to cause denial-of-service conditions on affected distributed motor controllers. CISA notes no known public exploitation has been reported, but Rockwell states no fix is available. Defenders must rely on network segmentation and access controls. The vulnerability carries a CVSS v4.0 base score of 8.7 (High), reflecting its remote-exploitable nature and lack of authentication requirements, though impact is limited to availability. Organizations using ArmorStart in critical manufacturing environments should prioritize isolating the affected systems from internet-facing networks and implementing defense-in-depth controls as patch availability is not expected.
Mentioned in this report
Detection guidance
Rockwell Studio 5000 Logix Designer Application Crash
Detects Windows Application Error (crash) events for Studio 5000 Logix Designer processes, a possible sign of the uncaught-exception DoS in the ArmorStart AOP COM interface. This is a low-confidence indicator because the advisory has no exploit telemetry. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Rockwell Studio 5000 Logix Designer Application Crash
id: e7797141-b90f-5629-b601-07e442f95676
status: experimental
description: Detects Application Error (event 1000) crash events for Studio 5000 Logix
Designer processes. An uncaught exception in the ArmorStart Add-On Profile COM method
handling (V2.05.07 and earlier) can crash the host process, so repeated crashes
on an engineering workstation warrant review. Correlate with inbound network activity
from unexpected hosts. Low-confidence indicator as no public exploitation is documented.
tags:
- attack.impact
- attack.t1499.004
logsource:
product: windows
service: application
detection:
selection:
Provider_Name: Application Error
EventID: 1000
Data|contains:
- LogixDesigner
- Studio5000
- Studio 5000
condition: selection
falsepositives:
- Ordinary Logix Designer instability, such as large project loads or plugin and add-on
profile incompatibilities
- Engineering workstations running unstable or beta Studio 5000 builds
level: low
author: Vorant
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-25-289-04
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-25-289-04
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 614 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs