CWE-651: Exposure of WSDL File Containing Sensitive Information

VariantIncomplete

The Web services architecture may require exposing a Web Service Definition Language (WSDL) file that contains information on the publicly accessible services and how callers of these services should interact with them (e.g. what parameters they expect and what types they return).

View on MITRE
Back to CWE Lookup

Extended Description

An information exposure may occur if any of the following apply: The WSDL file is accessible to a wider audience than intended. The WSDL file contains information on the methods/services that should not be publicly accessible or information about deprecated methods. This problem is made more likely due to the WSDL often being automatically generated from the code. Information in the WSDL file helps guess names/locations of methods/resources that should not be publicly accessible.

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-651 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-651, Exposure of WSDL File Containing Sensitive Information, 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

Apply Separation of Privilege controls for Exposure of WSDL File Containing Sensitive Information

MITRE associates mitigation with Architecture and Design; the listed strategies include Separation of Privilege; recorded impacts include Read Application Data. Use these source-defined anchors to turn CWE-651 into implementation, review, and verification checks for the affected component.

CWE-651: Exposure of WSDL File Containing Sensitive Information — MITRE CWE

Triage CWE-651 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-651, Exposure of WSDL File Containing Sensitive Information, 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-651

Apply MITRE's full root-cause mapping guidance when using CWE-651, Exposure of WSDL File Containing Sensitive Information. 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-651 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-651, Exposure of WSDL File Containing Sensitive Information. 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-651: Exposure of WSDL File Containing Sensitive Information?+

CWE-651: Exposure of WSDL File Containing Sensitive Information is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The Web services architecture may require exposing a Web Service Definition Language (WSDL) file that contains information on the publicly accessible services and how callers of these services should interact with them (e.g. what parameters they expect and what types they return). An information exposure may occur if any of the following apply: The WSDL file is accessible to a wider audience than intended. The WSDL file contains information on the methods/services that should not be publicly accessible or information about deprecated methods. This problem is made more likely due to the WSDL often being automatically generated from the code. Information in the WSDL file helps guess names/locations of methods/resources that should not be publicly accessible.

What are the security consequences of Exposure of WSDL File Containing Sensitive Information?+

If exploited, CWE-651 (Exposure of WSDL File Containing Sensitive Information) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

How do you prevent or mitigate Exposure of WSDL File Containing Sensitive Information?+

Recommended mitigations for CWE-651 include: Limit access to the WSDL file as much as possible. If services are provided only to a limited number of entities, it may be better to provide WSDL privately to each of these entities than to publish WSDL publicly. Make sure that WSDL does not describe methods that should not be publicly accessible. Make sure to protect service methods that should not be publicly accessible with access controls. Do not use method names in WSDL that might help an adversary guess names of private methods/resources used by the service.

Which programming languages are affected by Exposure of WSDL File Containing Sensitive Information?+

CWE-651 commonly affects Not Language-Specific. 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-651 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-651

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