CVE intelligence and bounded remediation

CVE-2022-29958 — JTEKT TOYOPUC PLCs through 2022-04-29 do not ensure data integrity

Critical CVSS 9.8

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.

Severity
Critical
CVSS
9.8 (3.1)
Published
2022-07-26
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-345

Affected products

  • jtekt / pc10g-cpu_tcc-6353_firmware
  • jtekt / pc10ge_tcc-6464_firmware
  • jtekt / pc10p_tcc-6372_firmware
  • jtekt / pc10p-dp_tcc-6726_firmware
  • jtekt / pc10p-dp-io_tcc-6752_firmware
  • jtekt / pc10b-p_tcc-6373_firmware

Showing 6 representative product identities from 17 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Supply-chain, dependency, build, and update integrity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
  • Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
  • Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.

Remediate safely

  • Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
  • Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
  • Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.