# CVE-2022-34151: Hardcoded credentials in Machine automation controller NJ series, Machine automation controller NX series, Automation software 'Sysmac Studio', and Programmable Terminal (PT) NA series

> Remote attackers can access OMRON industrial controllers and software by using hard-coded credentials found in the products.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jul 2022
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-gx2r-v5m4-v5qp

## What is CVE-2022-34151?

CVE-2022-34151 is a critical vulnerability in OMRON Corporation Machine automation controller NJ series, Machine automation controller NX series, Automation software 'Sysmac Studio', and Programmable Terminal (PT) NA series, published on 4 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of hard-coded credentials vulnerability exists in Machine automation controller NJ series all models V 1.48 and earlier, Machine automation controller NX7 series all models V1.28 and earlier, Machine automation controller NX1 series all models V1.48 and earlier, Automation software 'Sysmac Studio' all models V1.49 and earlier, and Programmable Terminal (PT) NA series NA5-15W/NA5-12W/NA5-9W/NA5-7W models Runtime V1.15 and earlier, which may allow a remote attacker who successfully obtained the user credentials by analyzing the affected product to access the controller.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-34151?

It affects 57 products.


Products: Omron Na5-12w Firmware, Omron Na5-15w Firmware, Omron Na5-7w Firmware, Omron Na5-9w Firmware, Omron Nj-Pa3001 Firmware, Omron Nj-Pd3001 Firmware, Omron Nj101-1000 Firmware, Omron Nj101-1020 Firmware, Omron Nj101-9000 Firmware, Omron Nj101-9020 Firmware, Omron Nj301-1100 Firmware, Omron Nj301-1200 Firmware, Omron Nj501-1300 Firmware, Omron Nj501-1320 Firmware, Omron Nj501-1340 Firmware, Omron Nj501-140 Firmware, Omron Nj501-1420 Firmware, Omron Nj501-1500 Firmware, Omron Nj501-1520 Firmware, Omron Nj501-4300 Firmware and 37 more.

## How do I fix CVE-2022-34151?

No fix has been published for CVE-2022-34151 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-34151 being exploited?

There is no known exploitation of CVE-2022-34151 in the wild and no public exploit code.

## Other vulnerabilities in OMRON Corporation Machine automation controller NJ series, Machine automation controller NX series, Automation software 'Sysmac Studio', and Programmable Terminal (PT) NA series

- [CVE-2022-33208](https://insights.sbomify.com/CVE-2022-33208/): Auth bypass in Machine automation controller NJ series, Machine automation controller NX series, Automation software 'Sysmac Studio', and Programmable Terminal (PT) NA series (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34151 and fix it if it is affected.

What it is: CVE-2022-34151 is a critical vulnerability in OMRON Corporation Machine automation controller NJ series, Machine automation controller NX series, Automation software 'Sysmac Studio', and Programmable Terminal (PT) NA series, published on 4 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34151 in the wild and no public exploit code.

Affected product: OMRON Corporation Machine automation controller NJ series, Machine automation controller NX series, Automation software 'Sysmac Studio', and Programmable Terminal (PT) NA series. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-34151/ (Markdown: https://insights.sbomify.com/CVE-2022-34151/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-34151
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-34151
- OSV: https://osv.dev/vulnerability/CVE-2022-34151

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-34151/
Summaries are generated and may contain mistakes; the official description above is the record.