CWE-313 Variante Borrador

Cleartext Storage in a File or on Disk

This vulnerability occurs when an application writes sensitive data, such as passwords or personal information, directly to a file or disk without using encryption.

Definición

What is CWE-313?

This vulnerability occurs when an application writes sensitive data, such as passwords or personal information, directly to a file or disk without using encryption.
When sensitive data is stored in plain text, anyone with access to the file—or even the raw disk—can read it directly. This includes attackers who have gained system access, malicious insiders, or even system administrators performing routine maintenance. The risk isn't limited to standard file permissions; physical access to a storage device or the ability to read disk sectors can also expose the unprotected information. Even if the data appears scrambled or uses a simple encoding like Base64, it does not provide real security. Attackers can easily detect common encoding schemes and reverse them to recover the original cleartext. True protection requires strong, standard encryption with a securely managed key, not just obfuscation, to ensure data remains confidential both at rest and if the storage medium is compromised.
Impacto en el mundo real

Real-world CVEs caused by CWE-313

  • CVE-2001-1481

    Cleartext credentials in world-readable file.

  • CVE-2005-1828

    Password in cleartext in config file.

  • CVE-2005-2209

    Password in cleartext in config file.

  • CVE-2002-1696

    Decrypted copy of a message written to disk given a combination of options and when user replies to an encrypted message.

  • CVE-2004-2397

    Cleartext storage of private key and passphrase in log file when user imports the key.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    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.

  2. 2

    This Java example shows a properties file with a cleartext username / password pair.

  3. 3

    The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.

  4. 4

    Username and password information should not be included in a configuration file or a properties file in cleartext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.

Ejemplo de código vulnerable

Vulnerable Java

This Java example shows a properties file with a cleartext username / password pair.

Vulnerable Java 
```
# Java Web App ResourceBundle properties file* 
  ...
  webapp.ldap.username=secretUsername
  webapp.ldap.password=secretPassword
  ...
Ejemplo de código seguro

Secure pseudo

Seguro 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 prevención

How to prevent CWE-313

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Señales de detección

How to detect CWE-313

Automated Static Analysis High

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.)

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-313 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-313?

This vulnerability occurs when an application writes sensitive data, such as passwords or personal information, directly to a file or disk without using encryption.

¿Qué gravedad tiene CWE-313?

MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.

¿Qué lenguajes o plataformas se ven afectados por CWE-313?

MITRE no ha especificado plataformas afectadas para esta CWE — puede aplicar a la mayoría de los stacks de aplicaciones.

¿Cómo puedo prevenir CWE-313?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

¿Cómo detecta y corrige Plexicus CWE-313?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-313 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.

¿Dónde puedo aprender más sobre CWE-313?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/313.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-313

CWE-312 Padre

Cleartext Storage of Sensitive Information

This vulnerability occurs when an application stores sensitive data like passwords, credit card numbers, or personal information in plain…

CWE-314 Hermano

Cleartext Storage in the Registry

This vulnerability occurs when an application saves sensitive data, like passwords or keys, as plain text in the Windows Registry.

CWE-315 Hermano

Cleartext Storage of Sensitive Information in a Cookie

This vulnerability occurs when an application directly stores sensitive data, like session tokens or personal details, in a browser cookie…

CWE-316 Hermano

Cleartext Storage of Sensitive Information in Memory

This vulnerability occurs when an application stores sensitive data, such as passwords or encryption keys, in memory without any form of…

CWE-317 Hermano

Cleartext Storage of Sensitive Information in GUI

This vulnerability occurs when an application stores sensitive data, such as passwords or personal information, in plain text within its…

CWE-318 Hermano

Cleartext Storage of Sensitive Information in Executable

This vulnerability occurs when an application embeds sensitive information, like passwords or keys, directly within its executable code…

CWE-526 Hermano

Cleartext Storage of Sensitive Information in an Environment Variable

This vulnerability occurs when an application stores sensitive data, such as passwords or API keys, as plain text in an environment…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo