CWE-258: Empty Password in Configuration File

Code Examples & CVEs

Demonstrative Examples

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 the password is provided as an empty string.

This Java example shows a properties file with an empty password string.

BadJava

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

This Java example shows a properties file with an empty password string.

BadASP.NET

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

Observed CVE Examples (1)

CVE-2022-26117

Network access control (NAC) product has a configuration file with an empty password

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-258 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-258, Empty Password in Configuration File, 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 Empty Password in Configuration File during System Configuration

MITRE associates mitigation with System Configuration; recorded impacts include Gain Privileges or Assume Identity; observed examples include CVE-2022-26117. Use these source-defined anchors to turn CWE-258 into implementation, review, and verification checks for the affected component.

CWE-258: Empty Password in Configuration File — MITRE CWE

Triage CWE-258 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-258, Empty Password in Configuration File, 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-258

Apply MITRE's full root-cause mapping guidance when using CWE-258, Empty Password in Configuration File. 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-258 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-258, Empty Password in Configuration File. 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-258: Empty Password in Configuration File?+

CWE-258: Empty Password in Configuration File is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Using an empty string as a password is insecure.

What are the security consequences of Empty Password in Configuration File?+

If exploited, CWE-258 (Empty Password in Configuration File) it can compromise Access Control, leading to outcomes such as Gain Privileges or Assume Identity.

How do you prevent or mitigate Empty Password in Configuration File?+

Recommended mitigations for CWE-258 include: Passwords should be at least eight characters long -- the longer the better. Avoid passwords that are in any way similar to other passwords you have. Avoid using words that may be found in a dictionary, names book, on a map, etc. Consider incorporating numbers and/or punctuation into your password. If you do use common words, consider replacing letters in that word with numbers and punctuation. However, do not use "similar-looking" punctuation. For example, it is not a good idea to change cat to c@t, ca+, (@+, or anything similar. Finally, it is never appropriate to use an empty string as a password.

Which programming languages are affected by Empty Password in Configuration File?+

CWE-258 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 Empty Password in Configuration File?+

MITRE documents real CVEs mapped to CWE-258, including CVE-2022-26117. 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-258 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-258: Empty Password in Configuration File

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods