LiveActive security incident?Get immediate response
CVE Record

CVE-2022-29951: JTEKT TOYOPUC PLCs through 2022-04-29 mishandle authentication.

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This flaw affects JTEKT TOYOPUC PLCs that expose the CMPLink/TCP engineering protocol. The protocol lacks authentication, so reachable attackers may perform sensitive PLC engineering actions. For operations leaders, the concern is unauthorized control or disruption of industrial equipment, not data theft.

Executive priority

Treat this as an urgent operational technology exposure review. Prioritize sites where TOYOPUC PLCs are reachable beyond tightly controlled engineering networks, because impact can include process disruption or unauthorized control changes.

Technical view

CVE-2022-29951 is CWE-306 missing authentication in TOYOPUC PLC CMPLink/TCP through 2022-04-29. The protocol can run over TCP or UDP on configurable ports 1024-65534 and supports engineering functions including PLC start/stop, project upload/download, and configuration changes. CVSS is 9.1 with network, no-auth attack conditions.

Likely exposure

Exposure is most likely in industrial sites using JTEKT TOYOPUC PLCs where CMPLink/TCP is reachable from untrusted networks, flat plant networks, remote access paths, or vendor engineering workstations.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. The risk is still severe because unauthenticated network reachability can allow integrity and availability impact against PLC operations.

Researcher notes

Public source data names the protocol behavior and impact class, but the supplied affected-product metadata is incomplete. Avoid assuming specific TOYOPUC models, firmware builds, patches, or exploitation until confirmed from vendor or CISA advisory details.

Mitigation direction

  • Check JTEKT and CISA guidance for supported updates, configuration changes, or compensating controls.
  • Restrict CMPLink/TCP access to authorized engineering hosts only.
  • Segment PLC networks from enterprise, internet, and remote-access networks.
  • Block unnecessary TCP and UDP ports in the 1024-65534 range to PLCs.
  • Monitor for unexpected engineering-protocol activity and unauthorized configuration changes.

Validation and detection

  • Inventory TOYOPUC PLCs and identify firmware or software status against vendor guidance.
  • Identify where CMPLink/TCP is enabled and which TCP or UDP ports are reachable.
  • Review firewall and segmentation rules protecting PLC engineering interfaces.
  • Confirm only approved engineering workstations can communicate with affected PLC ports.
  • Review PLC change history and engineering access records for suspicious activity.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-29951 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2022-29951Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.