Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Authentication Bypass in Rockwell Automation Logix Controllers

IdentifiersCVE-2021-22681CWE-522· Insufficiently Protected Credentials

CVE-2021-22681 affects Rockwell Automation Studio 5000 Logix Designer versions 21 and later and RSLogix 5000 versions 16 through 20 in their trust relationship with multiple Logix controller families, including CompactLogix, ControlLogix, GuardLogix, DriveLogix, and SoftLogix. The software uses a key-based mechanism to verify that Logix controllers are communicating with legitimate Rockwell engineering software. The vulnerability exists because this key is insufficiently protected and can be discovered or extracted, allowing an unauthenticated attacker to bypass the verification mechanism and authenticate to affected controllers as if they were an authorized workstation or application. Rockwell and CISA reporting indicate that successful exploitation can enable an unauthorized third-party tool or application to connect to the controller and interact with it as a trusted engineering endpoint.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to defeat the controller communication trust model and establish unauthorized authenticated communications with affected Logix controllers. This can enable modification of controller configuration and/or application code, extraction of project files, impersonation of trusted engineering workstations, and manipulation of PLC-controlled processes. In operational technology environments, this creates risk of process disruption, loss of control integrity, operational downtime, and potentially physical consequences depending on the controlled process.

Mitigation

If you can’t patch tonight, do this now.

Mitigate by removing affected PLCs and associated management interfaces from direct internet exposure; strictly limiting network reachability to controllers, especially industrial protocol access such as TCP/44818; segmenting OT networks from IT and untrusted zones; mediating remote access through secure gateways, firewalls, proxies, or VPNs; monitoring for anomalous engineering traffic and unauthorized controller connections; and placing controllers with physical mode switches into run position where operationally feasible to prevent remote modification. Disable unnecessary services and apply broader Rockwell OT hardening guidance. Because no patch is available, compensating controls are the primary defense.

Remediation

Patch, then assume compromise.

Rockwell Automation has indicated that no software patch exists for this vulnerability. Organizations should follow Rockwell guidance such as PN1550 and related hardening advisories, and implement compensating controls around affected controllers and engineering workstations. Where feasible, deploy CIP Security or Rockwell-recommended proxy/security controls, restrict access to affected controllers, and review vendor guidance for affected product families and configurations.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Rockwell AutomationFactorytalk Services Platformapplication
Rockwell AutomationRslogix 5000application
Rockwell AutomationStudio 5000 Logix Designerapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence1

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity17

Community discussion across Reddit, Mastodon, and other social sources.