Security readout for executives and security teams
Plain-English summary
Some AutomationDirect CLICK C0-1x PLC CPUs can stay unlocked after a legitimate programming session is interrupted. While unlocked, later programming connections may be accepted without authorization until a proper disconnect or power cycle occurs. For industrial environments, this creates serious risk to equipment integrity and availability.
Executive priority
Treat this as urgent for any site using affected CLICK PLCs in reachable production networks. Prioritize firmware verification, exposure reduction, and maintenance controls because unauthorized programming access can affect process availability and safety-adjacent operations.
Technical view
CVE-2021-32986 is an authentication bypass in CLICK PLC C0-1x CPU modules with firmware prior to v3.00. The unlocked state lacks a timeout after authorized access, and interruption of programming software can leave the PLC accepting subsequent programming connections without authorization. CVSS 3.1 is 9.8 with network attack vector and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where affected C0-1x PLC programming interfaces are reachable by untrusted networks or shared engineering networks. Risk also depends on whether authorized programming sessions can be interrupted without a clean disconnect.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The issue is still high risk because it is remotely reachable, requires no privileges after the device is left unlocked, and affects operational technology devices.
Researcher notes
Evidence supports an authentication bypass caused by persistent unlocked state rather than credential compromise. Sources do not provide exploit activity confirmation. Validation should focus on firmware, programming-session lifecycle, network reachability, and whether operational procedures reliably relock devices.
Mitigation direction
- Update affected C0-1x CPUs to firmware v3.00 or later where vendor guidance confirms applicability.
- Power cycle affected PLCs after interrupted programming sessions, following operational safety procedures.
- Ensure programming software disconnects cleanly after authorized maintenance.
- Restrict PLC programming access to trusted engineering hosts and managed networks.
- Review CISA and AutomationDirect guidance before applying site-specific compensating controls.
Validation and detection
- Inventory CLICK C0-1x CPU modules and record firmware versions.
- Identify devices running firmware prior to v3.00.
- Confirm programming interfaces are not reachable from untrusted networks.
- Review maintenance procedures for interrupted programming sessions and required relock steps.
- Check whether affected PLCs were power cycled after abnormal programming interruptions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-32986 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/uscert/ics/advisories/icsa-21-166-02CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.