CWE-261 Base Incompleto

Weak Encoding for Password

Using simple encoding like Base64 to hide a password provides no real security, as it can be easily reversed.

Definición

What is CWE-261?

Using simple encoding like Base64 to hide a password provides no real security, as it can be easily reversed.
This weakness occurs when developers try to protect passwords stored in configuration files or application properties by encoding them with schemes like Base64, hex, or ROT13. While this obscures the password from casual viewing, it is not encryption. Any attacker who discovers the encoded string can trivially decode it back to the original plaintext password, offering no meaningful defense. True password protection requires strong, one-way cryptographic hashing with a salt, or using a dedicated secrets management solution. Encoding is a form of security through obscurity that creates a false sense of safety. Developers should treat any encoded secret as if it were plaintext, because for an attacker, it effectively is.
Impacto en el mundo real

Real-world CVEs caused by CWE-261

Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    The following code reads a password from a properties file and uses the password to connect to a database.

  2. 2

    This code will run successfully, but anyone with access to config.properties can read the value of password and easily determine that the value has been base 64 encoded. If a devious employee has access to this information, they can use it to break into the system.

  3. 3

    The following code reads a password from the registry and uses the password to create a new network credential.

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

Ejemplo de código vulnerable

Vulnerable Java

The following code reads a password from a properties file and uses the password to connect to a database.

Vulnerable Java 
...
  Properties prop = new Properties();
  prop.load(new FileInputStream("config.properties"));
  String password = Base64.decode(prop.getProperty("password"));
  DriverManager.getConnection(url, usr, password);
  ...
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-261

  • Passwords should be encrypted with keys that are at least 128 bits in length for adequate security.
Señales de detección

How to detect CWE-261

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-261 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-261?

Using simple encoding like Base64 to hide a password provides no real security, as it can be easily reversed.

¿Qué gravedad tiene CWE-261?

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-261?

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-261?

Passwords should be encrypted with keys that are at least 128 bits in length for adequate security.

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

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-261 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-261?

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

Debilidades relacionadas

Weaknesses related to CWE-261

CWE-522 Padre

Insufficiently Protected Credentials

This vulnerability occurs when an application handles sensitive credentials like passwords or API keys in an insecure way, making them…

CWE-256 Hermano

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…

CWE-257 Hermano

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 Hermano

Password in Configuration File

This vulnerability occurs when an application stores sensitive passwords directly within a configuration file, making them easily readable…

CWE-523 Hermano

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 Hermano

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

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