CVE-2022-29951· NVD / CVE Program· CNA mitre

JTEKT TOYOPUC PLCs through 2022-04-29 mishandle authentication.

Noroxi assessment

Priority: Monitor (action score 36/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 70.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.1 · v3.1—No exploit No fix recorded

BDU:2022-03758

Published: Jul 26, 2022
Updated: Jun 17, 2026
EPSS: 1.3% · 70th percentile
CWE: CWE-306

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 36 / 40 · 9.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.3%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
jtekt	pc10g-cpu tcc-6353 firmware	cpe:2.3:o:jtekt:pc10g-cpu_tcc-6353_firmware
jtekt	pc10g-cpu tcc-6353	cpe:2.3:h:jtekt:pc10g-cpu_tcc-6353
jtekt	pc10ge tcc-6464 firmware	cpe:2.3:o:jtekt:pc10ge_tcc-6464_firmware
jtekt	pc10ge tcc-6464	cpe:2.3:h:jtekt:pc10ge_tcc-6464
jtekt	pc10p tcc-6372 firmware	cpe:2.3:o:jtekt:pc10p_tcc-6372_firmware
jtekt	pc10p tcc-6372	cpe:2.3:h:jtekt:pc10p_tcc-6372
jtekt	pc10p-dp tcc-6726 firmware	cpe:2.3:o:jtekt:pc10p-dp_tcc-6726_firmware
jtekt	pc10p-dp tcc-6726	cpe:2.3:h:jtekt:pc10p-dp_tcc-6726
jtekt	pc10p-dp-io tcc-6752 firmware	cpe:2.3:o:jtekt:pc10p-dp-io_tcc-6752_firmware
jtekt	pc10p-dp-io tcc-6752	cpe:2.3:h:jtekt:pc10p-dp-io_tcc-6752
jtekt	pc10b-p tcc-6373 firmware	cpe:2.3:o:jtekt:pc10b-p_tcc-6373_firmware
jtekt	pc10b-p tcc-6373	cpe:2.3:h:jtekt:pc10b-p_tcc-6373

and 22 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

jtekt nano 10gx tuc-1157 firmwareall versions
jtekt nano cpu tuc-6941 firmwareall versions
jtekt pc10b tcc-1021 firmwareall versions
jtekt pc10b-p tcc-6373 firmwareall versions
jtekt pc10e tcc-4737 firmwareall versions
jtekt pc10el tcc-4747 firmwareall versions
jtekt pc10g-cpu tcc-6353 firmwareall versions
jtekt pc10ge tcc-6464 firmwareall versions
jtekt pc10p tcc-6372 firmwareall versions
jtekt pc10p-dp tcc-6726 firmwareall versions
jtekt pc10p-dp-io tcc-6752 firmwareall versions
jtekt pc10pe tcc-1101 firmwareall versions
jtekt pc10pe-1616p tcc-1102 firmwareall versions
jtekt pc3jx tcc-6901 firmwareall versions
jtekt pc3jx-d tcc-6902 firmwareall versions
jtekt pcdl tkc-6688 firmwareall versions
jtekt plus cpu tcc-6740 firmwareall versions

Same product

jtekt: all records

Other highest-scoring records for the same primary product.

CVE-2022-29958JTEKT TOYOPUC PLCs through 2022-04-29 do not ensure data integrity.
39Monitor
CVE-2021-27458If Ethernet communication of the JTEKT Corporation TOYOPUC product series’ (TOYOPUC-PC10 Series: PC10G-CPU TCC-6353: All versions, PC10GE TC
30Monitor
CVE-2021-33011All versions of the afffected TOYOPUC-PC10 Series,TOYOPUC-Plus Series,TOYOPUC-PC3J/PC2J Series, TOYOPUC-Nano Series products may not be able
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-306 · Missing Authentication for Critical Function

CVSS vector

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

nvd-primary

Root cause

A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”

The bug in code

The whole CWE-306 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1// Added for the support team
2app.post("/maintenance/reset", resetDevice);

Fixed

1if (config.maintenanceEnabled) {
2  app.post(
3    "/maintenance/reset",
4    requireSession, requireRole("admin"), resetDevice
5  );
6}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.cisa.gov/uscert/ics/advisories/icsa-22-172-02

Show all references (1 more)

www.forescout.com/blog/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records