Security readout for executives and security teams
Plain-English summary
FactoryTalk Services Platform can fail to enforce FactoryTalk Security policies when those policies depend on computer name. An authenticated remote attacker could bypass intended restrictions and gain privileges equivalent to a user logged onto the client machine. This is most relevant to Rockwell-based industrial environments using affected FactoryTalk security deployments.
Executive priority
Treat this as a high-priority OT access-control issue where FactoryTalk supports production or safety-relevant operations. It is not confirmed as actively exploited in the provided sources, but the potential privilege impact warrants prompt inventory, vendor guidance review, and controlled remediation planning.
Technical view
CVE-2021-32960 affects Rockwell Automation FactoryTalk Services Platform v6.11 and earlier when FactoryTalk Security is enabled and deployed. The issue is a CWE-693 protection mechanism failure allowing a remote authenticated attacker to bypass computer-name-based security policies. CVSS 3.1 is 8.5 with network attack vector, low privileges required, high complexity, no user interaction, and high impact.
Likely exposure
Exposure is likely limited to organizations running FactoryTalk Services Platform v6.11 or earlier with FactoryTalk Security enabled and policies tied to computer name. The attacker requires authentication, but successful abuse could undermine access controls in sensitive industrial operations.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires network access, valid low-privileged authentication, and conditions involving computer-name-based FactoryTalk Security policy decisions.
Researcher notes
Key constraints are authenticated access, high attack complexity, and FactoryTalk Security configurations using computer-name-based policies. Evidence provided does not include exploit details, patch version, or public exploitation confirmation. Validate exposure through configuration review rather than assuming all FactoryTalk deployments are affected.
Mitigation direction
- Inventory FactoryTalk Services Platform versions and identify v6.11 or earlier deployments.
- Review Rockwell advisory 1131785 for vendor-approved fixes or configuration guidance.
- Avoid relying solely on computer-name-based FactoryTalk Security policies.
- Restrict network access to FactoryTalk services to trusted administrative and engineering systems.
- Apply CISA ICS guidance for segmentation and controlled remote access.
Validation and detection
- Confirm whether FactoryTalk Security is enabled on each FactoryTalk Services Platform deployment.
- Review policies that grant or deny access based on client computer name.
- Check installed FactoryTalk Services Platform versions against v6.11 and earlier.
- Verify vendor guidance has been applied and documented for affected systems.
- Review authentication logs for unexpected access from authorized accounts or client machines.
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-693: 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 lookupCVE-2021-32960 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
- High
- CVSS
- 8.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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:H/PR:L/UI:N/S:C/C:H/I:H/A:H1.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.5HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/uscert/ics/advisories/icsa-21-161-01CVE reference · x_refsource_CONFIRM
- https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1131785CVE 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.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.