Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-522 Class Incomplete
Insufficiently Protected Credentials
This vulnerability occurs when an application handles sensitive credentials like passwords or API keys in an insecure way, making them easy for attackers to steal during transmission or while stored.
Definition
What is CWE-522?
This vulnerability occurs when an application handles sensitive credentials like passwords or API keys in an insecure way, making them easy for attackers to steal during transmission or while stored.
Insufficiently protected credentials are a primary target for attackers. This happens when developers rely on weak or outdated methods, such as sending passwords in plain text over unencrypted connections (HTTP), storing them in easily accessible logs or public code repositories, or using weak encryption that can be easily reversed. Attackers exploit these flaws using simple network sniffing, searching public code commits, or accessing poorly secured databases to harvest credentials and gain unauthorized access.
To prevent this, always enforce strong, modern security practices. This means using TLS (HTTPS) for all credential transmission, never logging or caching passwords, and employing robust, salted hashing algorithms (like Argon2 or bcrypt) for storage. Additionally, implement secure credential management solutions, such as secrets managers or environment variables, to keep keys out of your application code entirely. Regular security audits and automated scanning can help catch these dangerous oversights before they are exploited.
Real-world impact
Real-world CVEs caused by CWE-522
-
A messaging platform serializes all elements of User/Group objects, making private information available to adversaries
-
Initialization file contains credentials that can be decoded using a "simple string transformation"
-
Python-based RPC framework enables pickle functionality by default, allowing clients to unpickle untrusted data.
-
Programmable Logic Controller (PLC) sends sensitive information in plaintext, including passwords and session tokens.
-
Building Controller uses a protocol that transmits authentication credentials in plaintext.
-
Programmable Logic Controller (PLC) sends password in plaintext.
-
Remote Terminal Unit (RTU) uses a driver that relies on a password stored in plaintext.
-
Web app allows remote attackers to change the passwords of arbitrary users without providing the original password, and possibly perform other unauthorized actions.
How attackers exploit it
Step-by-step attacker path
- 1
This code changes a user's password.
- 2
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.
- 3
The following code reads a password from a properties file and uses the password to connect to a database.
- 4
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.
- 5
The following code reads a password from the registry and uses the password to create a new network credential.
Vulnerable code example
Vulnerable PHP
This code changes a user's password.
$user = $_GET['user'];
$pass = $_GET['pass'];
$checkpass = $_GET['checkpass'];
if ($pass == $checkpass) {
SetUserPassword($user, $pass);
} Secure code example
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist
How to prevent CWE-522
- Architecture and Design Use an appropriate security mechanism to protect the credentials.
- Architecture and Design Make appropriate use of cryptography to protect the credentials.
- Implementation Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
Detection signals
How to detect CWE-522
Plexicus auto-detects CWE-522 and opens a fix PR in under 60 seconds.
Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.
Frequently asked questions What is CWE-522?
How serious is CWE-522?
What languages or platforms are affected by CWE-522?
How can I prevent CWE-522?
How does Plexicus detect and fix CWE-522?
Where can I learn more about CWE-522?
Frequently asked questions
What is CWE-522?
This vulnerability occurs when an application handles sensitive credentials like passwords or API keys in an insecure way, making them easy for attackers to steal during transmission or while stored.
How serious is CWE-522?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-522?
MITRE lists the following affected platforms: ICS/OT.
How can I prevent CWE-522?
Use an appropriate security mechanism to protect the credentials. Make appropriate use of cryptography to protect the credentials.
How does Plexicus detect and fix CWE-522?
Plexicus's SAST engine matches the data-flow signature for CWE-522 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-522?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/522.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-522
CWE-1390 Parent
Weak Authentication
This vulnerability occurs when a system's login or identity verification process is too easy to bypass or fool. While it attempts to check…
CWE-1391 Sibling
Use of Weak Credentials
This vulnerability occurs when a system relies on weak authentication credentials—like default passwords, hard-coded keys, or easily…
CWE-262 Sibling
Not Using Password Aging
This vulnerability occurs when a system lacks password expiration policies, allowing users to keep the same password indefinitely.
CWE-263 Sibling
Password Aging with Long Expiration
The system enforces password changes, but the time allowed between changes is excessively long, weakening security.
CWE-289 Sibling
Authentication Bypass by Alternate Name
This vulnerability occurs when a system checks access based on a resource or user name, but fails to account for all the different names…
CWE-290 Sibling
Authentication Bypass by Spoofing
This weakness occurs when an application's authentication system can be tricked into accepting forged or manipulated credentials, allowing…
CWE-294 Sibling
Authentication Bypass by Capture-replay
This vulnerability occurs when an attacker can intercept and record legitimate authentication traffic, then replay it later to gain…
CWE-301 Sibling
Reflection Attack in an Authentication Protocol
A reflection attack is a flaw in mutual authentication protocols that allows an attacker to impersonate a legitimate user without knowing…
CWE-302 Sibling
Authentication Bypass by Assumed-Immutable Data
This vulnerability occurs when an authentication system incorrectly treats certain data as unchangeable, when in fact an attacker can…
Ready when you are
Don't Let Security
Weigh You Down.
Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.