The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
N/A
Threat Mapped score: 1.8
Industry: Finiancial
Threat priority: P4 - Informational (Low)
CVE: CVE-2022-30018
A messaging platform serializes all elements of User/Group objects, making private information available to adversaries
CVE: CVE-2022-29959
Initialization file contains credentials that can be decoded using a "simple string transformation"
CVE: CVE-2022-35411
Python-based RPC framework enables pickle functionality by default, allowing clients to unpickle untrusted data.
CVE: CVE-2022-29519
Programmable Logic Controller (PLC) sends sensitive information in plaintext, including passwords and session tokens.
CVE: CVE-2022-30312
Building Controller uses a protocol that transmits authentication credentials in plaintext.
CVE: CVE-2022-31204
Programmable Logic Controller (PLC) sends password in plaintext.
CVE: CVE-2022-30275
Remote Terminal Unit (RTU) uses a driver that relies on a password stored in plaintext.
CVE: CVE-2007-0681
Web app allows remote attackers to change the passwords of arbitrary users without providing the original password, and possibly perform other unauthorized actions.
CVE: CVE-2000-0944
Web application password change utility doesn't check the original password.
CVE: CVE-2005-3435
product authentication succeeds if user-provided MD5 hash matches the hash in its database; this can be subjected to replay attacks.
CVE: CVE-2005-0408
chain: product generates predictable MD5 hashes using a constant value combined with username, allowing authentication bypass.
| Phase | Note |
|---|---|
| Architecture and Design | COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic. |
| Implementation | N/A |
Intro: This code changes a user's password.
Body: While the code confirms that the requesting user typed the same new password twice, it does not confirm that the user requesting the password change is the same user whose password will be changed. An attacker can request a change of another user's password and gain control of the victim's account.
$user = $_GET['user']; $pass = $_GET['pass']; $checkpass = $_GET['checkpass']; if ($pass == $checkpass) { SetUserPassword($user, $pass); }Intro: The following code reads a password from a properties file and uses the password to connect to a database.
Body: This code will run successfully, but anyone who has access to config.properties can read the value of password. If a devious employee has access to this information, they can use it to break into the system.
... Properties prop = new Properties(); prop.load(new FileInputStream("config.properties")); String password = prop.getProperty("password"); DriverManager.getConnection(url, usr, password); ...Intro: The following code reads a password from the registry and uses the password to create a new network credential.
Body: This code will run successfully, but anyone who has access to the registry key used to store the password can read the value of password. If a devious employee has access to this information, they can use it to break into the system
... String password = regKey.GetValue(passKey).toString(); NetworkCredential netCred = new NetworkCredential(username,password,domain); ...Intro: Both of these examples verify a password by comparing it to a stored compressed version.
Body: Because a compression algorithm is used instead of a one way hashing algorithm, an attacker can recover compressed passwords stored in the database.
int VerifyAdmin(char *password) { if (strcmp(compress(password), compressed_password)) { printf("Incorrect Password!\n"); return(0); } printf("Entering Diagnostic Mode...\n"); return(1); }Intro: The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.
Body: This Java example shows a properties file with a cleartext username / password pair.
# Java Web App ResourceBundle properties file ... webapp.ldap.username=secretUsername webapp.ldap.password=secretPassword ...Intro: In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.
Body: Multiple vendors used cleartext transmission or storage of passwords in their OT products.