CIP Just Became the Off Switch: Rockwell's Six-Advisory CISA Drop

On September 1, CISA quietly dropped six ICS advisories, and every single one of them pointed at the same company: Rockwell Automation. The batch covers RSLinx Classic, the Logix controller platform (ControlLogix, CompactLogix, GuardLogix, and the 5480s), Factory Historian ME, the Redundancy Module Configuration Tool, and FactoryTalk Activation Manager. The headline isn't the count. It's the protocol. Across the whole pile, the common attack surface is CIP, the Common Industrial Protocol, and a single crafted CIP message is enough to take things down. In RSLinx Classic, four different flaws (all versions 4.50 and below, CVSS 8.6) let a malformed or oversized CIP packet crash the service, and in the Logix platform an improper length check on a CIP message pushes the controller into a Major Non-Recoverable Fault. No credentials, no user click, no exploit chain. A packet on the wire is the whole attack.

Here's the part that should bother anyone who has ever stood in front of a dead panel. In an IT system, a denial of service means you restart the service or reboot the VM; the blast radius is a support ticket. In a Logix, the fault is latched. The controller holds the Major Non-Recoverable Fault state until you power-cycle it, and on a safety controller you need to re-download the program before it will run again. So the remote, unauthenticated, network-reachable DoS that takes 30 seconds to fire actually takes a human being walking across the plant floor to undo. Multiply that by the fact that the affected Logix firmware runs back to V33 and the RSLinx line to 4.50, versions most plants have been sitting on for years because revalidating a controller upgrade is a project, not a patch Tuesday.

U.S. flag
Source image 1

The practical read is less scary, which is the point. Nobody is being actively exploited, there's no CISA KEV entry, no public weapon, and fixes exist for most of it: RSLinx Classic 4.60, Logix 34.015 or later (or 35.014, 36.013, 37.011), and FactoryTalk Activation Manager 5.03. The Historian ME remote code execution and the Redundancy Module Configuration Tool local privilege escalations are the ones worth a closer look, because one needs only low-level authentication and the other just wants a standard user to drop a DLL in a writable directory. But the bigger shift is that the CIP layer itself has effectively become the trust boundary for a lot of plants, and anything that

Source article image
Source image 2
speaks CIP fluently enough to look legitimate can now knock a line offline on demand. If your shop is running V34 or older, what does it actually cost you to upgrade, and has anyone ever tested whether a power cycle is the whole recovery or the first line item on a bigger incident? I'd like to think you have. Tell me what you found.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more