CENTUM CS 3000: Incorrect Permission Assignment for Critical Resource
CVE-2022-22148 is a high-severity incorrect permission assignment for critical resource vulnerability in CENTUM CS 3000 from Yokogawa Electric, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected CENTUM CS 3000 versions: versions from R3.08.10 to R3.09.00. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Centum Vp Firmware to r6.09.00 or a later version.
- Update Centum Vp Entry Firmware to r6.09.00 or a later version.
- Read the advisory on web-material3.yokogawa.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Yokogawa Electric | CENTUM CS 3000 | versions from R3.08.10 to R3.09.00 | Not stated |
| Yokogawa Electric | CENTUM VP | versions from R4.01.00 to R4.03.00; versions from R5.01.00 to R5.04.20; versions from R6.01.00 to R6.08.00 | Not stated |
| Yokogawa Electric | Exaopc | versions from R3.72.00 to R3.79.00 | Not stated |
| Yokogawa | Centum Cs 3000 Firmware | r3.08.10 through r3.09.00 | Not stated |
| Yokogawa | Centum Cs 3000 Entry Firmware | r3.08.10 through r3.09.00 | Not stated |
| Yokogawa | Centum Vp Firmware | r4.01.00 through r4.03.00; r5.01.00 through r5.04.20; r6.01.00 up to, but not including, r6.09.00 | r6.09.00 |
| Yokogawa | Centum Vp Entry Firmware | r4.01.00 through r4.03.00; r5.01.00 through r5.04.20; r6.01.00 up to, but not including, r6.09.00 | r6.09.00 |
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
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 2.0 | 6.9 | Medium | NVD |
Official description
'Root Service' service implemented in the following Yokogawa Electric products creates some named pipe with improper ACL configuration. CENTUM CS 3000 versions from R3.08.10 to R3.09.00, CENTUM VP versions from R4.01.00 to R4.03.00, from R5.01.00 to R5.04.20, and from R6.01.00 to R6.08.00, Exaopc versions from R3.72.00 to R3.79.00.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in CENTUM CS 3000
- 8.5 High severity
- 7.8 High severity
- 8.8 High severity
- 8.1 High severity
- 8.1 High severity
- 7.8 High severity
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 7.6 High severity
- 9.1 Critical severity
- 7.3 High severity
- 7.8 High severity
- 7.8 High severity
- 4.3 Medium severity
Spotted an error? Tell us.