CWE-261 Base Incomplet

Weak Encoding for Password

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

Définition

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.

Impact réel

Real-world CVEs caused by CWE-261

Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

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

Exemple de code vulnérable

Vulnerable Java

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

Vulnérable Java

...
  Properties prop = new Properties();
  prop.load(new FileInputStream("config.properties"));
  String password = Base64.decode(prop.getProperty("password"));
  DriverManager.getConnection(url, usr, password);
  ...

Exemple de code sécurisé

Secure pseudo

Sécurisé 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.

Liste de contrôle de prévention

How to prevent CWE-261

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

Signaux de détection

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

CWE-261

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.

Request AI Swarm Pentest

Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-261 ?

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

Quelle est la gravité de CWE-261 ?

MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.

Quels langages ou plateformes sont affectés par CWE-261 ?

MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.

Comment puis-je prévenir CWE-261 ?

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

Comment Plexicus détecte et corrige CWE-261 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-261 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-261 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/261.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-261

CWE-522 Parent

Prêt à valider ce qui compte.

Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.

Réserver un Pentest

Weak Encoding for Password

What is CWE-261?

Real-world CVEs caused by CWE-261

Parcours de l'attaquant étape par étape

Vulnerable Java

Secure pseudo

How to prevent CWE-261

How to detect CWE-261

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-261

Insufficiently Protected Credentials

Plaintext Storage of a Password

Storing Passwords in a Recoverable Format

Password in Configuration File

Unprotected Transport of Credentials

Missing Password Field Masking

Further reading

Prêt à valider ce qui compte.

Vérifiez si l'AI Swarm Pentest convient à votre environnement.

Demande reçue. Réservez la prochaine étape.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`