CWE-651: Exposure of WSDL File Containing Sensitive Information
Description
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).
Submission Date :
Jan. 30, 2008, midnight
Modification Date :
2023-06-29 00:00:00+00:00
Organization :
Cigital
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.
Example - 1
The WSDL for a service providing information on the best price of a certain item exposes the following method: float getBestPrice(String ItemID) An attacker might guess that there is a method setBestPrice (String ItemID, float Price) that is available and invoke that method to try and change the best price of a given item to their advantage. The attack may succeed if the attacker correctly guesses the name of the method, the method does not have proper access controls around it and the service itself has the functionality to update the best price of the item.
Related Weaknesses
This table shows the weaknesses and high level categories that are related to this weakness. These relationships are defined to give an overview of the different insight to similar items that may exist at higher and lower levels of abstraction.
Visit http://cwe.mitre.org/ for more details.