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: 5733ddf49ff49cd1aad035497dcdc18d756b7520618af780e68758580dc93da7
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/health
GET /api/v1/product
GET /api/v1/product/orderInformation
GET /api/v1/product/{productIdentifier}
GET /api/v1/provider
GET /api/v1/provider/{providerCode}/location
GET /api/v1/version
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: 5733ddf49ff49cd1aad035497dcdc18d7d0e3c997d0e3c997d0e3c997d0e3c99
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /api/v1/health GET /api/v1/version