CVE-2022-45793 json
Executable files writable by low-privileged users in Omron Sysmac Studio
published 2024-01-10 2 y ago modified 2026-06-17 4 mo ago also EUVD-2022-48649
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
Sysmac Studio installs executables in a directory with poor permissions. This can allow a locally-authenticated attacker to overwrite files which will result in code execution with privileges of a different user.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-23-262-04 updated cvss 5.5
Omron Engineering Software
-
Omron Sysmac Studio <= 1.54affected: mitigation “OMRON recommends the following general mitigation measures to minimize the risk of exploitation of this vulnerability:” fa.omron.co.jp
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Omron Sysmac Studio
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
fa.omron.co.jp
/product/security/assets/pdf/en/OMSR-2023-009_en.pdf
vendor-advisory
-
cisa.gov
/news-events/ics-advisories/icsa-23-262-04
third-party-advisory, us-government-resource
-
dragos.com
/advisory/omron-plc-and-engineering-software-network-and-file-format-access/
third-party-advisory
Sources
- CVE List CVE-2022-45793
- NVD CVE-2022-45793
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.