CVE-2022-29951
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJTEKT 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJTEKT TOYOPUC PLCs through April 2022 use the CMPLink/TCP protocol (configurable on ports 1024-65534 over TCP or UDP) for critical engineering operations including starting/stopping the PLC, uploading/downloading projects, and modifying configuration. This protocol has no built-in authentication, enabling any network-adjacent attacker who can reach the affected ports to execute these functions without credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the PLC modelQuery the device or consult asset inventory to determine if the PLC is a JTEKT TOYOPUC model: Pc10g Cpu Tcc 6353, Pc10ge Tcc 6464, Pc10p Tcc 6372, Pc10p Dp Tcc 6726, Pc10p Dp Io Tcc 6752, Pc10b P Tcc 6373, Pc10b Tcc 1021, or Pc10e Tcc 4737Affected if The device is any of these JTEKT TOYOPUC PLC models
-
Verify CMPLink/TCP port availabilityScan the device for open TCP or UDP ports in the range 1024-65534. Use a network scanner or check firewall rules to identify if these ports are listeningAffected if Any CMPLink/TCP ports in the 1024-65534 range are open and listening on the PLC
-
Assess network exposureReview network segmentation and firewall rules to determine if the CMPLink/TCP ports are accessible from untrusted network segments. Check if ports are reachable from outside the trusted engineering workstation zoneAffected if CMPLink/TCP ports are accessible from network segments beyond trusted engineering stations
-
Confirm protocol usageAttempt a test connection to an open CMPLink/TCP port or examine network traffic to verify the CMPLink protocol is in use for engineering operationsAffected if CMPLink/TCP protocol is actively used for PLC operations such as start/stop, project transfer, or configuration changes
If the device is a listed JTEKT TOYOPUC PLC model with CMPLink/TCP ports (1024-65534) exposed on the network, the environment is affected by this unauthenticated protocol vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict network segmentation and firewall rules to restrict access to CMPLink/TCP ports (1024-65534) to only authorized engineering stations; coordinate with the vendor for patched firmware versions when available.
- Consultation6.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29951 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data