Unauthenticated programming access via persistent unlocked state
Published Apr 4, 2022 · Updated Apr 16, 2025
Authentication bypass in AutomationDirect CLICK PLC firmware before 3.00 allows remote attackers to make unauthorized programming connections. The controller fails to expire its unlocked state when the programming software is interrupted, so later programming sessions inherit authorization. Exploitation requires an authorized user to unlock the PLC before the client terminates abnormally; later unauthenticated sessions retain programming access.
Summary
What happened
Authentication bypass in AutomationDirect CLICK PLC firmware before 3.00 allows remote attackers to make unauthorized programming connections. The controller fails to expire its unlocked state when the programming software is interrupted, so later programming sessions inherit authorization. Exploitation requires an authorized user to unlock the PLC before the client terminates abnormally; later unauthenticated sessions retain programming access.
The record
- CVE
- CVE-2021-32986
- Published
- Apr 4, 2022
- Updated
- Apr 16, 2025
- Vendor
- AutomationDirect
- Product
- CLICK PLC
- Classifications
- CWE-863, CWE-288, T0866
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.00
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo