Controledge Plc Firmware: Use of Hard-coded Credentials
CVE-2022-30318 is a critical-severity use of hard-coded credentials vulnerability in Controledge Plc Firmware from Honeywell, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version r151.2 as the first without the flaw, so updating Controledge Plc Firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.85% chance of exploitation within 30 days, higher than 79% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Controledge Plc Firmware to r151.2 or a later version.
- Update Controledge Rtu Firmware to r151.2 or a later version.
- 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 |
|---|---|---|---|
| Honeywell | Controledge Plc Firmware | before r151.2 | r151.2 |
| Honeywell | Controledge Rtu Firmware | before r151.2 | r151.2 |
Version data comes from NVD's product matching. 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
- 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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
Honeywell ControlEdge through R151.1 uses Hard-coded Credentials. According to FSCT-2022-0056, there is a Honeywell ControlEdge hardcoded credentials issue. The affected components are characterized as: SSH. The potential impact is: Remote code execution, manipulate configuration, denial of service. The Honeywell ControlEdge PLC and RTU product line exposes an SSH service on port 22/TCP. Login as root to this service is permitted and credentials for the root user are hardcoded without automatically changing them upon first commissioning. The credentials for the SSH service are hardcoded in the firmware. The credentials grant an attacker access to a root shell on the PLC/RTU, allowing for remote code execution, configuration manipulation and denial of service.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Credentials
The product contains hard-coded credentials, such as a password or cryptographic key.
How developers prevent this class of flaw
- For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible. In Windows environments, the Encrypted File System (EFS) may provide some protection.
- For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a first login mode that requires the user to enter a unique strong password or key.
- If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
More Use of Hard-coded Credentials vulnerabilities (CWE-798)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/uscert/ics/advisories/icsa-22-242-06Third Party Advisory, US Government Resource
Other references
- forescout.com/blog/Not Applicable
Recent Use of Hard-coded Credentials vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.2 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.