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: 5733ddf49ff49cd1aad0354902484db139456753eabb22853c8337a5dfb325cb
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /LIVINS/{shortUrl}
GET /LIVSVC/{shortUrl}
GET /api/User/get
GET /api/v{version}/Shorten
GET /{shortUrl}
POST /api/User/create
POST /api/User/createapiKey
POST /api/User/update
Severity: info
Fingerprint: 5733ddf49ff49cd1f3d88d609c49b7489c9569d63f510282787684ecadd2fc7a
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /LIVINS/{shortUrl}
GET /LIVSVC/{shortUrl}
GET /api/User/get
GET /api/v{version}/Shorten
GET /{shortUrl}
POST /api/User/create
POST /api/User/createapiKey
POST /api/User/update