USE OF HARD-CODED CRYPTOGRAPHIC KEY CWE-321
The cryptographic key utilized to help protect the account password is hard coded into the RSLogix 500 binary file. An attacker could identify cryptographic keys and use it for further cryptographic attacks that could ultimately lead to a remote attacker gaining unauthorized access to the controller.
USE OF A BROKEN OR RISKY ALGORITHM FOR PASSWORD PROTECTION USE OF CLIENT-SIDE AUTHENTICATION CWE-327
The cryptographic function utilized to protect the password in MicroLogix is discoverable.
USE OF CLIENT-SIDE AUTHENTICATION CWE-603
A remote, unauthenticated attacker can send a request from the RSLogix 500 software to the victim’s MicroLogix controller. The controller will then respond to the client with used password values to authenticate the user on the client-side. This method of authentication may allow an attacker to bypass authentication altogether, disclose sensitive information, or leak credentials.
CLEARTEXT STORAGE OF SENSITIVE INFORMATION CWE-312
If Simple Mail Transfer Protocol (SMTP) account data is saved in RSLogix 500, a local attacker with access to a victim’s project may be able to gather SMTP server authentication data as it is written to the project file in cleartext.
CVSS v3 9.8
https://www.us-cert.gov/ics/advisories/icsa-20-070-06