Safeguard
Vulnerability Analysis•

CVE-2020-24682: High Unquoted Search Path in B&R Automation Studio

CVE-2020-24682 is a high unquoted search path flaw in B&R Automation Studio and NET/PVI. Update to the fixed 4.7, 4.8 or 4.9 releases in bulletin 2021-14.

Safeguard Security Team
3 min read

CVE-2020-24682 is a high severity (CVSS 7.2) unquoted search path flaw in B&R Automation Studio and NET/PVI that lets programs run with elevated privileges. Fixed releases are 4.7.7 SP, 4.8.6 SP and 4.9.4 SP for Automation Studio, and 4.7.7, 4.8.6 and 4.9.4 for NET/PVI.

What's affected

  • Automation Studio from 4.0 through 4.6, 4.7.0 before 4.7.7 SP, 4.8.0 before 4.8.6 SP, and 4.9.0 before 4.9.4 SP.
  • NET/PVI from 4.0 through 4.6, 4.7.0 before 4.7.7, 4.8.0 before 4.8.6, and 4.9.0 before 4.9.4.
  • Per the record. Confirm in B&R bulletin 2021-14.

The record scores it 7.2 (High) with vector CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.

How to check if you're exposed

Check Automation Studio under Help, About. For NET/PVI check the installed program entry in Windows Settings under Apps. On Windows you can also review service definitions for unquoted paths that contain spaces with the service control tools.

What to do now

  1. Inventory machines with Automation Studio or NET/PVI.
  2. Read versions.
  3. Install the fixed release for your line.
  4. Restrict write access to the root of the system drive and program folders.
  5. Audit services on those machines for unquoted paths.

After you patch, record the new version for B&R Automation Studio and NET/PVI in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.

Why it matters

The record maps the flaw to CWE-428, unquoted search path or element. When a Windows service path with spaces is not wrapped in quotes, the system may try shorter paths first. A user who can drop a file in one of those locations may get it run with the service's higher rights.

The fix is a vendor update, and it pairs with CVE-2020-24681 in the same bulletin.

To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.

Quick check

Why does a missing quote matter?

On Windows, an unquoted service path with spaces is parsed ambiguously. If a user can write to an earlier part of the path, their file can be run at the service's privilege level.

How do I find every place B&R Automation Studio and NET/PVI is used?

Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.

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.