CWE-259: Use of Hard-coded Password

Extended Description

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.

Mitigation Strategies

Phase

Architecture and Design

Description

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.

Phase

Architecture and Design

Description

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.

Phase

Architecture and Design

Description

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.

Phase

Architecture and Design

Description

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.

Phase

Architecture and Design

Description

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.

Code Examples & CVEs

Demonstrative Examples

The following code uses a hard-coded password to connect to a database:

This is an example of an external hard-coded password on the client-side of a connection. This code will run successfully, but anyone who has access to it will have access to the password. Once the program has shipped, there is no going back from the database user "scott" with a password of "tiger" unless the program is patched. A devious employee with access to this information can use it to break into the system. Even worse, if attackers have access to the bytecode for application, they can use the javap -c command to access the disassembled code, which will contain the values of the passwords used. The result of this operation might look something like the following for the example above:

BadJava

...DriverManager.getConnection(url, "scott", "tiger");...

The following code is an example of an internal hard-coded password in the back-end:

Every instance of this program can be placed into diagnostic mode with the same password. Even worse is the fact that if this program is distributed as a binary-only distribution, it is very difficult to change that password or disable this "functionality."

BadC

int VerifyAdmin(char *password) {                         if (strcmp(password, "Mew!")) {                                                                 printf("Incorrect Password!\n");return(0);                            }printf("Entering Diagnostic Mode...\n");return(1);                      }

The following code is an example of an internal hard-coded password in the back-end:

BadJava

int VerifyAdmin(String password) {if (!password.equals("Mew!")) {return(0);}//Diagnostic Modereturn(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.

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

BadJava

# Java Web App ResourceBundle properties file                      ...webapp.ldap.username=secretUsernamewebapp.ldap.password=secretPassword...

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.

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

BadASP.NET

...<connectionStrings><add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /></connectionStrings>...

Observed CVE Examples (3)

CVE-2022-29964

Distributed Control System (DCS) has hard-coded passwords for local shell access

View Details

CVE-2021-37555

Telnet service for IoT feeder for dogs and cats has hard-coded password [REF-1288]

View Details

CVE-2021-35033

Firmware for a WiFi router uses a hard-coded password for a BusyBox shell, allowing bypass of authentication through the UART port

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-259 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-259, Use of Hard-coded Password, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Use of Hard-coded Password during Architecture and Design

MITRE associates mitigation with Architecture and Design; documented detection approaches include Manual Analysis, Black Box, and Automated Static Analysis; recorded impacts include Gain Privileges or Assume Identity, Hide Activities, and Reduce Maintainability. Use these source-defined anchors to turn CWE-259 into implementation, review, and verification checks for the affected component.

CWE-259: Use of Hard-coded Password — MITRE CWE

Triage CWE-259 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-259, Use of Hard-coded Password, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-259

Apply MITRE's full root-cause mapping guidance when using CWE-259, Use of Hard-coded Password. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-259 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-259, Use of Hard-coded Password. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-259: Use of Hard-coded Password?+

CWE-259: Use of Hard-coded Password is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. 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.

What are the security consequences of Use of Hard-coded Password?+

If exploited, CWE-259 (Use of Hard-coded Password) it can compromise Access Control, leading to outcomes such as Gain Privileges or Assume Identity, Hide Activities and Reduce Maintainability.

How do you prevent or mitigate Use of Hard-coded Password?+

Recommended mitigations for CWE-259 include: 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. 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. 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.

How is Use of Hard-coded Password detected?+

CWE-259 can be detected using Manual Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Use of Hard-coded Password?+

CWE-259 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Use of Hard-coded Password?+

MITRE documents real CVEs mapped to CWE-259, including CVE-2022-29964, CVE-2021-37555 and CVE-2021-35033. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-259 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-259: Use of Hard-coded Password

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Scope

Impact

Mitigation Strategies

Phase

Description

Phase

Description

Phase

Description

Phase

Description

Phase

Description

Detection Methods

Method

Description

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (3)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-259 with SSDF evidence

Address Use of Hard-coded Password during Architecture and Design

Triage CWE-259 against known exploitation evidence

Apply precise root-cause mapping to CWE-259

Validate CWE-259 with root-cause mapping checks

Frequently Asked Questions

Learn More