CWE-259: Use of Hard-coded Password
The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.
How it's found
Use of Hard-coded Password is a specific, narrowly defined instance of a broader pattern. Testers confirm it with targeted code review and a proof-of-concept input that exercises the exact code path this weakness describes.
There are two main variations of a hard-coded password:Inbound: the product contains an authentication mechanism that checks for a hard-coded password. Outbound: the product connects to another system or component, and it contains a hard-coded password for connecting to that component.
Consequences
- Gain Privileges or Assume Identity: If hard-coded passwords are used, it is almost certain that malicious users can gain access through the account in question.
- Gain Privileges or Assume Identity, Hide Activities, Reduce Maintainability: A hard-coded password typically leads to a significant authentication failure that can be difficult for the system administrator to detect. Once detected, it can be difficult to fix, so the administrator may be forced into disabling the product entirely.
Mitigations
- Architecture and Design: For outbound authentication: store passwords outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible.
- Architecture and Design: For inbound authentication: Rather than hard-code a default username and password for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password.
- Architecture and Design: Perform access control checks and limit which entities can access the feature that requires the hard-coded password. For example, a feature might only be enabled through the system console instead of through a network connection.
- Architecture and Design: For inbound authentication: apply strong one-way hashes to your passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When receiving an incoming password during authentication, take the hash of the password and compare it to the hash that you have saved. Use randomly assigned salts for each separate hash that you generate. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
- Architecture and Design: For front-end to back-end connections: Three solutions are possible, although none are complete.The first suggestion involves the use of generated passwords which are changed automatically and must be entered at given time intervals by a system administrator. These passwords will be held in memory and only be valid for the time intervals. Next, the passwords used should be limited at the back end to only performing actions valid for the front end, as opposed to having full access. Finally, the messages sent should be tagged and checksummed with time sensitive values so as to prevent replay style attacks.
How TurboPentest tests for this (white-box)
This weakness (Use of Hard-coded Password) is caught by white-box static analysis when you connect a GitHub repo: IntegSec's Opengrep SAST rule pack carries 4 rules for it, flagging the issue directly in your source code as part of the pentest.
Frequently asked questions
What is CWE-259?
The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.
How do you find Use of Hard-coded Password?
Use of Hard-coded Password is a specific, narrowly defined instance of a broader pattern. Testers confirm it with targeted code review and a proof-of-concept input that exercises the exact code path this weakness describes.
What is the impact of CWE-259?
Gain Privileges or Assume Identity: If hard-coded passwords are used, it is almost certain that malicious users can gain access through the account in question. Gain Privileges or Assume Identity, Hide Activities, Reduce Maintainability: A hard-coded password typically leads to a significant authentication failure that can be difficult for the system administrator to detect. Once detected, it can be difficult to fix, so the administrator may be forced into disabling the product entirely.
Does TurboPentest test for Use of Hard-coded Password?
This weakness (Use of Hard-coded Password) is caught by white-box static analysis when you connect a GitHub repo: IntegSec's Opengrep SAST rule pack carries 4 rules for it, flagging the issue directly in your source code as part of the pentest.
Related CWEs
- Base weaknessCWE-798: Use of Hard-coded Credentials
- Variant weaknessCWE-321: Use of Hard-coded Cryptographic Key
- Base weaknessCWE-257: Storing Passwords in a Recoverable Format
- Class weaknessCWE-287: Improper Authentication
- Base weaknessCWE-309: Use of Password System for Primary Authentication
- Class weaknessCWE-345: Insufficient Verification of Data Authenticity
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