CVE-2020-24681 is a high severity (CVSS 8.2) incorrect permission assignment flaw in B&R Industrial Automation Automation Studio that allows privilege escalation. Per the record, 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 are affected. The 4.6 line is also listed.
What's affected
- Automation Studio from 4.6.0 through 4.6.X, from 4.7.0 before 4.7.7 SP, from 4.8.0 before 4.8.6 SP, and from 4.9.0 before 4.9.4 SP, per the record.
- Fixed: 4.7.7 SP, 4.8.6 SP and 4.9.4 SP. The record gives no fixed 4.6 release, so 4.6 users should read B&R's bulletin 2021-14 for guidance.
The record scores it 8.2 (High) with vector CVSS:3.1/AV:L/AC:L/PR:L/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
Open Automation Studio and read the version under Help, then About. Compare it with the ranges above.
What to do now
- Inventory engineering workstations that run Automation Studio.
- Read the version on each.
- Move to the fixed service pack in your major line.
- If you are on 4.6, read B&R's bulletin and plan a move to a supported line.
- Limit who can log in to engineering workstations.
After you patch, record the new version for B&R Automation Studio 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-732, incorrect permission assignment for a critical resource. A resource that the software relies on is writable by users who should not change it, which lets a low privilege user gain more.
This sits on engineering workstations that program industrial controllers. The related issue CVE-2020-24682 comes from the same B&R bulletin and has the same fixed versions.
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
Which related issue shares this bulletin?
CVE-2020-24682, an unquoted search path flaw in Automation Studio and NET/PVI, is covered by the same B&R bulletin.
How do I find every place B&R Automation Studio 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.