CWE-13: ASP.NET Misconfiguration: Password in Configuration File

Code Examples & CVEs

Demonstrative Examples

The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database, but the pair is stored in plaintext.

Username and password information should not be included in a configuration file or a properties file in plaintext as this will allow anyone who can read the file access to the resource. If possible, encrypt this information.

BadASP.NET

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

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-13 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-13, ASP.NET Misconfiguration: 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 ASP.NET Misconfiguration: Password in Configuration File during Implementation

MITRE associates mitigation with Implementation; recorded impacts include Gain Privileges or Assume Identity; related weaknesses include CWE-260. Use these source-defined anchors to turn CWE-13 into implementation, review, and verification checks for the affected component.

CWE-13: ASP.NET Misconfiguration: Password in Configuration File — MITRE CWE

Triage CWE-13 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-13, ASP.NET Misconfiguration: 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-13

Apply MITRE's full root-cause mapping guidance when using CWE-13, ASP.NET Misconfiguration: 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-13 with root-cause mapping checks

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

CWE-13: ASP.NET Misconfiguration: Password in Configuration File is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource making them an easy target for attackers.

What are the security consequences of ASP.NET Misconfiguration: Password in Configuration File?+

If exploited, CWE-13 (ASP.NET Misconfiguration: 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 ASP.NET Misconfiguration: Password in Configuration File?+

Recommended mitigations for CWE-13 include: Credentials stored in configuration files should be encrypted, Use standard APIs and industry accepted algorithms to encrypt the credentials stored in configuration files.

Which programming languages are affected by ASP.NET Misconfiguration: Password in Configuration File?+

CWE-13 commonly affects ASP.NET. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

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

A CWE (Common Weakness Enumeration) like CWE-13 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-13: ASP.NET Misconfiguration: Password in Configuration File

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods