
ReDoc API Docs Exposure Scanner
This scanner detects the use of ReDoc API Docs Exposure in digital assets.
Short Info
Level
Single Scan
Single Scan
Can be used by
Asset Owner
Estimated Time
10 seconds
Time Interval
17 days 3 hours
Scan only one
URL
Toolbox
-
ReDoc is a popular service used for generating API documentation from OpenAPI specifications. It is widely used by developers and organizations that build RESTful APIs, providing a user-friendly interface for API documentation. ReDoc simplifies the process of understanding and implementing API functionalities for developers. It is integrated into various applications to enhance the visibility and understanding of API endpoints. Organizations leverage ReDoc for its ease of use and comprehensive feature set in showcasing API capabilities. It is a crucial tool in modern software development environments for ensuring that API documentation is accessible and comprehensible.
The vulnerability detected pertains to the exposure of API documentation through the ReDoc interface. This exposure can occur when the ReDoc documentation interface is accessible without proper authentication mechanisms in place. Such exposure might lead to unauthorized access to information about the API endpoints, which can be exploited by malicious actors. The vulnerability is categorized as an information exposure risk, as it may reveal sensitive details about the API structure and operations. This vulnerability is particularly concerning when API documentation is inadvertently left accessible to the public. By detecting this vulnerability, organizations can take preventive actions to safeguard their API information.
The technical details of the vulnerability revolve around the accessibility of the ReDoc documentation interface. This exposure can be detected by checking specific endpoints such as {{BaseURL}}/redoc or {{BaseURL}}/docs that host the API documentation. The vulnerable parameter is the lack of access control or authentication on these documentation URLs. When accessed, these endpoints can deliver content types identified by "text/html" and might contain specific strings like "__REDOC_EXPORT" or "redoc.standalone.js". Ensuring that these endpoints are secured against unauthorized access is crucial to prevent data exposure.
If exploited, this vulnerability can lead to several adverse outcomes. Unauthorized individuals may gain insights into API functionalities, which can be used to craft sophisticated attacks. Exposure of endpoint information can expedite the process for attackers to explore weaknesses in the API. The documentation might reveal operational details, leading to potential data breaches or unauthorized access to backend systems. Exploitation of this vulnerability increases the risk of exploitation of associated APIs. Furthermore, it can result in reputational damage if sensitive information becomes publicly accessible.
REFERENCES