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: 5733ddf49ff49cd1aad035494039cbcd6f6414b41a7390ffde38396e7f75a4a7
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/sync/jobs
GET /api/sync/jobs/{jobId}
GET /api/sync/jobs/{jobId}/result
POST /api/Sync/batch-sync-v2-to-v3
POST /api/Sync/create-v2
POST /api/Sync/sync-by-document
POST /api/Sync/sync-by-guid
POST /api/Sync/sync-by-id
POST /api/Sync/sync-by-id-v3
POST /api/Sync/sync-v2-to-v3
POST /api/Sync/sync-v3-to-v2