CVE-2022-31206
No exploitation reported by the sources we read.
- Published2022-07-26
- Fixed in1.49
- WeaknessCWE-347
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The Omron SYSMAC Nx product family PLCs (NJ series, NY series, NX series, and PMAC series) through 2022-005-18 lack cryptographic authentication. These PLCs are programmed using the SYMAC Studio engineering software (which compiles IEC 61131-3 conformant POU code to native machine code for execution by the PLC's runtime). The resulting machine code is executed by a runtime, typically controlled by a real-time operating system. The logic that is downloaded to the PLC does not seem to be cryptographically authenticated, allowing an attacker to manipulate transmitted object code to the PLC and execute arbitrary machine code on the processor of the PLC's CPU module in the context of the runtime. In the case of at least the NJ series, an RTOS and hardware combination is used that would potentially allow for memory protection and privilege separation and thus limit the impact of code execution. However, it was not confirmed whether these sufficiently segment the runtime from the rest of the RTOS.
Timeline
dates in UTC- 2022-07-2622:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-31206?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-31206?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.49 | < 1.49 | 1.49 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.49 | < 1.49 | 1.49 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.49 | < 1.49 | 1.49 | NVD |
22 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Omron SYSMAC CS/CJ/CP Series and NJ/NX Series
CP1W-CIF41: All versions · SYSMAC CJ2H: Versions prior to 1.5 · SYSMAC CJ2M: Versions prior to 2.1 · +5 more
Fix
- Update Omron nj101-1000 firmware to 1.49
- Mitigation from the vendor CISA ICSA-22-179-02 · 8 productsFor CVE-2022-31206: Omron intends to publish an update for SYSMAC NJ/NX in July 2022.
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDweakness (CWE)CWE-347read 2026-10-23
- FIRST EPSSEPSS score1.1 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2022-07-26
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-31206?
Is CVE-2022-31206 actively exploited?
What is the CVSS score for CVE-2022-31206?
Running Omron SYSMAC CS/CJ/CP Series? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.