VariantIncomplete

CWE-651Exposure of WSDL File Containing Sensitive Information

Category: data-exposure

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

Common consequences· 1

  • Confidentiality — Read Application Data
    The attacker may find sensitive information located in the WSDL file.

Potential mitigations· 3

  • [Architecture and Design]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.
  • [Architecture and Design]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.
  • [Architecture and Design]Do not use method names in WSDL that might help an adversary guess names of private methods/resources used by the service.

References

  1. https://cwe.mitre.org/data/definitions/651.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Inclusion of Sensitive Information in Test Code
CWE
Use of HTTP Request With Sensitive Query String
CWE
Inclusion of Sensitive Information in an Include File
CWE
Insertion of Sensitive Information Into Sent Data
CWE
Use of Web Browser Cache Containing Sensitive Information
CWE
Exposure of Sensitive Information Due to Incompatible Policies
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.