CWE-260: Password in Configuration File

Description

The product stores a password in a configuration file that might be accessible to actors who do not know the password.

This can result in compromise of the system for which the password is used. An attacker could gain access to this file and learn the stored password or worse yet, change the password to one of their choosing.

Potential Impact

Access Control

Gain Privileges or Assume Identity

Demonstrative Examples

Below is a snippet from a Java properties file.

Bad

webapp.ldap.username = secretUsernamewebapp.ldap.password = secretPassword

Because the LDAP credentials are stored in plaintext, anyone with access to the file can gain access to the resource.

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.

Bad

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

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 cleartext.

Bad

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

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

Mitigations & Prevention

Architecture and Design

Avoid storing passwords in easily accessible locations.

Architecture and Design

Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.

Detection Methods

Automated Static Analysis High — Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then sea

Real-World CVE Examples

CVE ID	Description
CVE-2022-38665	A continuous delivery pipeline management tool stores an unencypted password in a configuration file.

Taxonomy Mappings

7 Pernicious Kingdoms: — Password Management: Password in Configuration File

Frequently Asked Questions

What is CWE-260?

CWE-260 (Password in Configuration File) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The product stores a password in a configuration file that might be accessible to actors who do not know the password.

How can CWE-260 be exploited?

Attackers can exploit CWE-260 (Password in Configuration File) to gain privileges or assume identity. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.

How do I prevent CWE-260?

Key mitigations include: Avoid storing passwords in easily accessible locations.

What is the severity of CWE-260?

CWE-260 is classified as a Base-level weakness (Medium abstraction). It has been observed in 1 real-world CVEs.