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-256 Base Incompleto
Plaintext Storage of a Password
This vulnerability occurs when an application stores user passwords as readable text instead of using secure, one-way hashing. This insecure practice exposes credentials in memory, files, or…
Definição
What is CWE-256?
This vulnerability occurs when an application stores user passwords as readable text instead of using secure, one-way hashing. This insecure practice exposes credentials in memory, files, or databases where attackers can easily retrieve them.
Storing passwords in plaintext is a critical security failure because it completely bypasses the fundamental purpose of password protection. If an attacker gains access to the storage—through a database breach, a leaked file, or a memory dump—they immediately obtain all user credentials. This often leads to account takeover, data theft, and lateral movement across systems, as users frequently reuse passwords.
To prevent this, developers must never store the actual password. Instead, always use a strong, adaptive cryptographic hash function (like Argon2, scrypt, or bcrypt) with a unique salt for each password. This transforms the password into a fixed-length, irreversible string. Even if the hash is exposed, the original password remains computationally infeasible to recover, significantly limiting the damage of a data breach.
Impacto no mundo real
Real-world CVEs caused by CWE-256
-
Remote Terminal Unit (RTU) uses a driver that relies on a password stored in plaintext.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
The following code reads a password from a properties file and uses the password to connect to a database.
- 2
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.
- 3
The following code reads a password from the registry and uses the password to create a new network credential.
- 4
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
- 5
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.
Exemplo de código vulnerável
Vulnerable Java
The following code reads a password from a properties file and uses the password to connect to a database.
...
Properties prop = new Properties();
prop.load(new FileInputStream("config.properties"));
String password = prop.getProperty("password");
DriverManager.getConnection(url, usr, password);
... Exemplo de código seguro
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.
Lista de verificação de prevenção
How to prevent CWE-256
- Architecture and Design Avoid storing passwords in easily accessible locations.
- Architecture and Design Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
- A programmer might attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password because the encoding can be detected and decoded easily.
Sinais de deteção
How to detect CWE-256
CWE-256
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Perguntas frequentes O que é o CWE-256?
Qual a gravidade do CWE-256?
Que linguagens ou plataformas são afetadas pelo CWE-256?
Como posso prevenir o CWE-256?
Como é que o Plexicus deteta e corrige o CWE-256?
Onde posso saber mais sobre o CWE-256?
Frequently asked questions
O que é o CWE-256?
This vulnerability occurs when an application stores user passwords as readable text instead of using secure, one-way hashing. This insecure practice exposes credentials in memory, files, or databases where attackers can easily retrieve them.
Qual a gravidade do CWE-256?
A MITRE classifica a probabilidade de exploração como Alta — esta fraqueza é ativamente explorada em campo e deve ser priorizada para remediação.
Que linguagens ou plataformas são afetadas pelo CWE-256?
MITRE lists the following affected platforms: ICS/OT.
Como posso prevenir o CWE-256?
Avoid storing passwords in easily accessible locations. Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
Como é que o Plexicus deteta e corrige o CWE-256?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-256 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-256?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/256.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-256
CWE-522 Pai
Insufficiently Protected Credentials
This vulnerability occurs when an application handles sensitive credentials like passwords or API keys in an insecure way, making them…
CWE-257 Irmão
Storing Passwords in a Recoverable Format
This vulnerability occurs when an application stores user passwords in a format that can be easily reversed or decrypted back to their…
CWE-260 Irmão
Password in Configuration File
This vulnerability occurs when an application stores sensitive passwords directly within a configuration file, making them easily readable…
CWE-261 Irmão
Weak Encoding for Password
Using simple encoding like Base64 to hide a password provides no real security, as it can be easily reversed.
CWE-523 Irmão
Unprotected Transport of Credentials
This vulnerability occurs when a login page or authentication system transmits user credentials (like usernames and passwords) over a…
CWE-549 Irmão
Missing Password Field Masking
This vulnerability occurs when an application fails to hide password characters as they are typed, making them visible to anyone who can…
Recursos
Further reading
- MITRE — CWE-256 oficial https://cwe.mitre.org/data/definitions/256.html
- Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf
- OT:ICEFALL: The legacy of "insecure by design" and its implications for certifications and risk management https://www.forescout.com/resources/ot-icefall-report/
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.