CWE-261: Weak Encoding for Password
Obscuring a password with a trivial encoding does not protect the password.
How it's found
Weak Encoding for Password is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. A programmer can 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.
Consequences
- Gain Privileges or Assume Identity
Mitigations
- Passwords should be encrypted with keys that are at least 128 bits in length for adequate security.
Where this fits in a TurboPentest engagement
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Frequently asked questions
What is CWE-261?
Obscuring a password with a trivial encoding does not protect the password.
How do you find Weak Encoding for Password?
Weak Encoding for Password is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-261?
Gain Privileges or Assume Identity
Does TurboPentest test for Weak Encoding for Password?
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Related CWEs
- Class weaknessCWE-522: Insufficiently Protected Credentials
- Variant weaknessCWE-14: Compiler Removal of Code to Clear Buffers
- Class weaknessCWE-311: Missing Encryption of Sensitive Data
- Variant weaknessCWE-321: Use of Hard-coded Cryptographic Key
- Class weaknessCWE-326: Inadequate Encryption Strength
- Class weaknessCWE-327: Use of a Broken or Risky Cryptographic Algorithm
Written and reviewed by
Michel Chamberland - Founder & CEO, IntegSec
CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security
Michel has spent 20+ years on offensive security teams including IBM X-Force Red and Trustwave SpiderLabs, leading penetration tests, red team engagements, and breach response for Fortune 500 customers. He is the founder of IntegSec and the architect of TurboPentest.
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a pentest