# CVE-2022-29951: Missing authorization in n/a

> Attackers can modify PLC configurations and control operations because the CMPLink/TCP protocol lacks authentication mechanisms.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 27 Oct 2024
- **Also known as:** GHSA-c7f2-2769-qw43

## What is CVE-2022-29951?

CVE-2022-29951 is a critical missing authorization 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 mishandle authentication. They utilize the CMPLink/TCP protocol (configurable on ports 1024-65534 on either TCP or UDP) for a wide variety of engineering purposes such as starting and stopping the PLC, downloading and uploading projects, and changing configuration settings. This protocol does not have any authentication features, allowing any attacker capable of communicating with the port in question to invoke (a subset of) desired functionality.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

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-29951?

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

## Is CVE-2022-29951 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29958](https://insights.sbomify.com/CVE-2022-29958/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29951 is a critical missing authorization 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-29951 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-29951/ (Markdown: https://insights.sbomify.com/CVE-2022-29951/index.md)
```

## Sources

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

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