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).
Modes of Introduction:
– Architecture and Design
Related Weaknesses
CWE-538
Consequences
Confidentiality: Read Application Data
The attacker may find sensitive information located in the WSDL file.
Potential Mitigations
Phase: Architecture and Design
Description:
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.
Phase: Architecture and Design
Description:
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.
Phase: Architecture and Design
Description:
Do not use method names in WSDL that might help an adversary guess names of private methods/resources used by the service.
CVE References
