Safeguard
Vulnerability Analysis•

CVE-2021-22281: Medium Zip Slip in B&R Automation Studio

CVE-2021-22281 is a Zip Slip path traversal in B&R Automation Studio 4 project import. Only open trusted projects and follow the B&R mitigations.

Safeguard Security Team
3 min read

CVE-2021-22281 is a medium severity (CVSS 6.3) path traversal, known as Zip Slip, in B&R Automation Studio project import. Opening a crafted project can add or change files on the local system. B&R lists no fixed version in its advisory and recommends workarounds, including opening only trusted projects.

What's affected

  • B&R Industrial Automation Automation Studio. The NVD record says versions 4.0 through 4.12, and the B&R advisory says all versions of Automation Studio 4 are affected. We read these as the same set, but the advisory wording is broader.
  • B&R advisory 11/2021, first published 29 October 2021, rates the flaw 6.3 (Medium), the same as the record.
  • The advisory does not name a patched release. Its corrective action is to apply the listed workarounds.
  • The impact is on files writable by the Automation Studio user. The vector needs user interaction, because someone has to open the project.
  • KEV status: false.

How to check if you're exposed

Open Automation Studio and read the version under the help or about screen. Any 4.x release is covered by the advisory. Then look at how projects reach your engineers: shared drives, email attachments, vendor deliveries, and project backups stored on PLCs.

The question to ask is not only which version you run, but whether anyone opens project files from sources you do not control.

What to do now

  1. Open only Automation Studio project files that come from a trusted source.
  2. Use encrypted export of project files where possible, so that only legitimate users can access them.
  3. Protect the locations where projects are stored, including PLCs when you use the feature that backs up project source on the target.
  4. Do not run Automation Studio in elevated mode, and keep Windows User Account Control enabled.
  5. Verify the integrity of project files that travel through insecure channels, for example by checking a checksum sent separately.
  6. Check the B&R cyber security page for any later update to the advisory.

Why it matters

The classes are CWE-22, path traversal, and CWE-23, relative path traversal. Archive formats store file names, and a malicious archive can include names with directory climbing sequences. A tool that extracts without checking where each file lands can be tricked into writing outside the folder it intended. That pattern is known as Zip Slip.

In industrial settings the engineering workstation is a valuable target, because it holds the programs that run machines. A file written with the privileges of the engineer can change what gets downloaded to a controller. The advisory advice to avoid elevated mode and to trust only known project sources is practical because it limits what a bad file can reach.

Quick check

Is there a patch?

The B&R advisory we read names no fixed version. It recommends workarounds, so check B&R for any later guidance.

Does this need a network attacker?

The attacker must get a crafted project in front of a user who opens it. The mitigations focus on controlling where project files come from.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.