Security readout for executives and security teams
Plain-English summary
B&R Automation Studio project files can trigger code injection and local code execution when processed. This matters because engineering workstations used for industrial automation may bridge business IT and operational environments. The issue is high severity, but the provided sources do not show known active exploitation.
Executive priority
Treat this as a high-priority engineering workstation risk. Prioritize teams using Automation Studio with third-party project exchange or broad OT access, while confirming vendor remediation guidance before operational changes.
Technical view
CVE-2021-22282 is CWE-94 improper control of code generation in B&R Industrial Automation Automation Studio. The CVSS 3.1 score is 8.3 high, with user interaction required and high confidentiality, integrity, and availability impact. The bundle states Automation Studio 4.0 through 4.12 are affected.
Likely exposure
Exposure is most likely on engineering workstations that use B&R Automation Studio, especially where users open project files from external parties, vendors, integrators, shared repositories, or email attachments.
Exploitation context
The sources support code execution through crafted Automation Studio project files and do not indicate CISA KEV listing or active exploitation. User interaction is required according to the CVSS vector.
Researcher notes
Evidence is source-limited. The narrative description says versions 4.0 through 4.12 are affected, while the structured affected entry only lists version 4.0 with default unaffected status. Validate version scope against B&R’s advisory before asserting exposure.
Mitigation direction
- Check B&R’s advisory for fixed versions or vendor-recommended mitigations.
- Inventory Automation Studio installations and identify versions 4.0 through 4.12.
- Restrict opening Automation Studio projects from untrusted sources.
- Handle received project files through established malware-screening workflows.
- Limit engineering workstation privileges and access to sensitive OT networks.
Validation and detection
- Confirm installed Automation Studio versions on engineering workstations.
- Review whether external project files are accepted by email, portals, or shared drives.
- Check vendor advisory status against deployed versions.
- Review endpoint logs for suspicious execution from Automation Studio workflows.
- Verify engineering workstation segmentation from critical OT assets.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-22282 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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:N/UI:R/S:C/C:H/I:H/A:H1.66Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Source materials
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.