Safeguard
Vulnerability Analysis•

CVE-2022-45793: Medium Weak Permissions in Omron Sysmac Studio

CVE-2022-45793 is a medium severity permissions flaw in Omron Sysmac Studio 1.54 and earlier that allows local code execution. Apply Omron's fix.

Safeguard Security Team
3 min read

CVE-2022-45793 is a medium severity (CVSS 5.5) flaw in Omron Sysmac Studio 1.54 and prior. The installer places executables in a folder that low privileged users can write to, so a local user can replace them and run code as another user. Apply Omron's fix from advisory OMSR-2023-009.

What's affected

CISA advisory ICSA-23-262-04, published on 19 September 2023, lists Sysmac Studio version 1.54 and prior as affected. The NVD record, published on 10 January 2024, carries no version range, so the CISA text is the better guide to scope.

Source conflict worth knowing: NVD tags the weakness as CWE-276 (incorrect default permissions), while CISA labels it CWE-285 (improper authorization). Both describe the same behavior, executables installed with write access for low privileged users. Omron's own advisory is OMSR-2023-009; I could not read its contents, so confirm the fixed release there.

How to check if you're exposed

Open Sysmac Studio and read the version in the Help menu, About dialog. Anything at 1.54 or earlier is in the affected range per CISA.

To see the permission problem itself on a Windows machine, look at the access control list on the installation folder, for example with icacls pointed at the Sysmac Studio install directory. If ordinary users hold write or modify rights on folders that contain executables, the machine matches the issue description.

What to do now

  1. Inventory Sysmac Studio installs and note each version.
  2. Upgrade to the version Omron names in OMSR-2023-009, or apply the vendor's stated workaround.
  3. Tighten the access control list on the install directory so only administrators can modify executables, if Omron's guidance allows it.
  4. Limit who can log in to engineering workstations, since the attacker needs a local account.
  5. Follow CISA's general ICS guidance on network segmentation and defense in depth.

Why it matters

The root issue is a trust boundary mistake. Installers that place program files in a location writable by standard users let any such user swap a binary. When another user, or a service, later runs that binary, the attacker's code runs with that identity. The class is covered by CWE-276.

CISA states that no known public exploitation specifically targeting this vulnerability has been reported to it, and that the flaw is not exploitable remotely. The record's KEV flag is false. The practical risk is a shared engineering workstation where several people log in with different rights.

Quick check

Which Sysmac Studio versions are affected?

CISA lists version 1.54 and prior. Check Omron's advisory OMSR-2023-009 for the fixed release.

Can this be exploited over the network?

CISA says it is not exploitable remotely. The attacker needs local access with a low privileged account.

Sources

You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.

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.