Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1b885ff43a0a0e27f0caf932a9a8a33844143bc8a7d7a85ff
Public Swagger UI/API detected at path: /swagger.json - sample paths:
DELETE /devicestatus/{spec}
DELETE /treatments/{spec}
GET /devicestatus/
GET /echo/{storage}/{spec}
GET /entries
GET /entries/{spec}
GET /profile
GET /slice/{storage}/{field}/{type}/{prefix}/{regex}
GET /status
GET /times/echo/{prefix}/{regex}
GET /times/{prefix}/{regex}
GET /treatments