# CVE-2022-29958: Code injection in n/a

> Attackers can inject arbitrary machine code into JTEKT TOYOPUC PLCs via unauthenticated CMPLink/TCP protocol, gaining full control over the CPU module.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 26 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vq3c-fhqv-p29r

## What is CVE-2022-29958?

CVE-2022-29958 is a critical code injection vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JTEKT TOYOPUC PLCs through 2022-04-29 do not ensure data integrity. They utilize the unauthenticated CMPLink/TCP protocol for engineering purposes, including downloading projects and control logic to the PLC. Control logic is downloaded to the PLC on a block-by-block basis with a given memory address and a blob of machine code. The logic that is downloaded to the PLC is not cryptographically authenticated, allowing an attacker to execute arbitrary machine code on the PLC's CPU module in the context of the runtime. In the case of the PC10G-CPU, and likely for other CPU modules of the TOYOPUC family, a processor without MPU or MMU is used and this no memory protection or privilege-separation capabilities are available, giving an attacker full control over the CPU.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 17 products.


Products: Jtekt Nano 10gx Tuc-1157 Firmware, Jtekt Nano Cpu Tuc-6941 Firmware, Jtekt Pc10b-P Tcc-6373 Firmware, Jtekt Pc10b Tcc-1021 Firmware, Jtekt Pc10e Tcc-4737 Firmware, Jtekt Pc10el Tcc-4747 Firmware, Jtekt Pc10g-Cpu Tcc-6353 Firmware, Jtekt Pc10ge Tcc-6464 Firmware, Jtekt Pc10p-Dp-Io Tcc-6752 Firmware, Jtekt Pc10p-Dp Tcc-6726 Firmware, Jtekt Pc10p Tcc-6372 Firmware, Jtekt Pc10pe-1616p Tcc-1102 Firmware, Jtekt Pc10pe Tcc-1101 Firmware, Jtekt Pc3jx-D Tcc-6902 Firmware, Jtekt Pc3jx Tcc-6901 Firmware, Jtekt Pcdl Tkc-6688 Firmware, Jtekt Plus Cpu Tcc-6740 Firmware.

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

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

## Is CVE-2022-29958 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29951](https://insights.sbomify.com/CVE-2022-29951/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29958 is a critical code injection vulnerability in n/a, published on 26 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-29958 in the wild and no public exploit code.

Affected product: n/a. 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-29958/ (Markdown: https://insights.sbomify.com/CVE-2022-29958/index.md)
```

## Sources

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

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