pc10g-cpu_tcc-6353_firmware: Missing Authentication for Critical Functionality
CVE-2022-29951 is a critical-severity missing authentication for critical functionality vulnerability in pc10g-cpu_tcc-6353_firmware from Jtekt, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected pc10g-cpu_tcc-6353_firmware versions: all versions. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.32% chance of exploitation within 30 days, higher than 71% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of pc10g-cpu_tcc-6353_firmware you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Jtekt | pc10g-cpu_tcc-6353_firmware | all versions | Not stated |
| Jtekt | Pc10ge Tcc-6464 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10p Tcc-6372 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10p-dp Tcc-6726 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10p-dp-io Tcc-6752 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10b-p Tcc-6373 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10b Tcc-1021 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10e Tcc-4737 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10el Tcc-4747 Firmware | Not specified in the record | Not stated |
| Jtekt | Plus Cpu Tcc-6740 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc3jx Tcc-6901 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc3jx-d Tcc-6902 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10pe Tcc-1101 Firmware | Not specified in the record | Not stated |
| Jtekt | Pc10pe-1616p Tcc-1102 Firmware | Not specified in the record | Not stated |
| Jtekt | Pcdl Tkc-6688 Firmware | Not specified in the record | Not stated |
| Jtekt | Nano 10gx Tuc-1157 Firmware | Not specified in the record | Not stated |
| Jtekt | Nano Cpu Tuc-6941 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.1 | Critical | NVD |
| CVSS 3.1 | 9.1 | Critical | CISA (ADP) |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- cisa.gov/uscert/ics/advisories/icsa-22-172-02Mitigation, Third Party Advisory, US Government Resource
Third-party and government advisories
- forescout.com/blog/Third Party Advisory
Other vulnerabilities in pc10g-cpu_tcc-6353_firmware
- 9.8 Critical severity
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.1 Critical severity
- 7.5 High severity
- 7.8 High severity
- 9.1 Critical severity
- 7.8 High severity
- 7.5 High severity
Spotted an error? Tell us.