CWE-540: Inclusion of Sensitive Information in Source Code

BaseIncomplete

Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.

View on MITRE
Back to CWE Lookup

Extended Description

There are situations where it is critical to remove source code from an area or server. For example, obtaining Perl source code on a system allows an attacker to understand the logic of the script and extract extremely useful information such as code bugs or logins and passwords.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-540 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-540, Inclusion of Sensitive Information in Source Code, 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 Inclusion of Sensitive Information in Source Code during Architecture and Design

MITRE associates mitigation with Architecture and Design, and System Configuration; documented detection approaches include Automated Static Analysis; recorded impacts include Read Application Data. Use these source-defined anchors to turn CWE-540 into implementation, review, and verification checks for the affected component.

CWE-540: Inclusion of Sensitive Information in Source Code — MITRE CWE

Triage CWE-540 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-540, Inclusion of Sensitive Information in Source Code, 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-540

Apply MITRE's full root-cause mapping guidance when using CWE-540, Inclusion of Sensitive Information in Source Code. 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-540 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-540, Inclusion of Sensitive Information in Source Code. 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-540: Inclusion of Sensitive Information in Source Code?+

CWE-540: Inclusion of Sensitive Information in Source Code is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Source code on a web server or repository often contains sensitive information and should generally not be accessible to users. There are situations where it is critical to remove source code from an area or server. For example, obtaining Perl source code on a system allows an attacker to understand the logic of the script and extract extremely useful information such as code bugs or logins and passwords.

What are the security consequences of Inclusion of Sensitive Information in Source Code?+

If exploited, CWE-540 (Inclusion of Sensitive Information in Source Code) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

How do you prevent or mitigate Inclusion of Sensitive Information in Source Code?+

Recommended mitigations for CWE-540 include: Recommendations include removing this script from the web server and moving it to a location not accessible from the Internet.

Which programming languages are affected by Inclusion of Sensitive Information in Source Code?+

CWE-540 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 Inclusion of Sensitive Information in Source Code?+

MITRE documents real CVEs mapped to CWE-540, including CVE-2022-25512, CVE-2022-24867 and CVE-2007-6197. 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-540 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.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-540

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement