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: 5733ddf49ff49cd1aad0354927d8d0f011d11062dfeebafc1fa1a8bf1fa1a8bf
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /Capex/api/GeneralLedgerByBusinessUnitSAQApi GET /Capex/orch/CreateBusinessUnit POST /SalesForce/api/encode POST /api/Login/gettoken
GraphQL introspection is enabled.
This could leak to data leak if not properly configured.
Severity: medium
Fingerprint: c2db3a1c40d490db2337d3d603073f8703073f8703073f8703073f8703073f87
GraphQL introspection enabled at /api/graphql Detected: GitLab
Severity: medium
Fingerprint: c2db3a1c40d490db2337d3d62337d3d62337d3d62337d3d62337d3d62337d3d6
GraphQL introspection enabled at /api/graphql
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: 5733ddf49ff49cd1aad035491e60a468d1ecaedad5142bab10bac1983ca96c72
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/Members
GET /api/Members/GetModifiedMembers
GET /api/Members/GetRelatedAccountInfos
GET /api/Members/{id}
GET /api/SalesData/{id}
POST /api/Members/RegisterUpsertMember
POST /api/SalesData
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: 5733ddf49ff49cd1aad035491e60a468d1ecaedad5142bab10bac1983ca96c72
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/Members
GET /api/Members/GetModifiedMembers
GET /api/Members/GetRelatedAccountInfos
GET /api/Members/{id}
GET /api/SalesData/{id}
POST /api/Members/RegisterUpsertMember
POST /api/SalesData
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: 5733ddf49ff49cd1aad0354982b0e721ccca0a3eccca0a3eccca0a3eccca0a3e
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /outputcache/{region}
GET /configuration