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: 5733ddf49ff49cd1f5e22fb432102bf597b167883434c445bfb7225e177f9444
Public Swagger UI/API detected at path: /api/swagger.json - sample paths:
GET /.endpoints/login
GET /.endpoints/set-cookie
GET /.endpoints/tenants
GET /health
GET /heartbeat
GET /{p*}
POST /.endpoints/token
POST /import
POST /import/{p*}
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: 5733ddf49ff49cd1f5e22fb4f51c9fd4803403d502521d28e29187d48649b36d
Public Swagger UI/API detected at path: /api/swagger.json - sample paths:
GET /.endpoints/access
GET /.endpoints/login
GET /.endpoints/set-cookie
GET /.endpoints/tenantVaultInfo/{tenantId}
GET /.endpoints/tenants
GET /health
GET /heartbeat
GET /{p*}
POST /.endpoints/service-accounts/token
POST /import
POST /import/{p*}
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: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
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: 5733ddf49ff49cd1a8bcc6e5693072147997ac6b00d4aafe91ab2b3b91ab2b3b
Public Swagger UI/API detected at path: /webjars/swagger-ui/index.html - sample paths:
DELETE /search/deleteNewsByAutoNos
GET /healthCheck
GET /search/deleteOldNews
GET /search/{category}/{query}
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: 5733ddf49ff49cd1a8bcc6e5693072147997ac6b00d4aafe91ab2b3b91ab2b3b
Public Swagger UI/API detected at path: /webjars/swagger-ui/index.html - sample paths:
DELETE /search/deleteNewsByAutoNos
GET /healthCheck
GET /search/deleteOldNews
GET /search/{category}/{query}
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: 5733ddf49ff49cd1aad035493b3b73504d58962b5567fe97fb9d7cf8e4aedd96
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /
GET /v1/accounts
GET /v1/accounts/dapper
GET /v1/accounts/dapper/proc/{id}
GET /v1/accounts/dapper/{id}
GET /v1/accounts/odata
GET /v1/accounts/{id}
GET /v1/accounts/{id}/variant-async
GET /v1/accounts/{id}/variant-sync
GET /v1/accountstable
GET /v1/clients
GET /v1/publish
GET /v1/subscribe
GET /v1/test/context
GET /v1/test/di
GET /v1/test/httpcall
GET /v1/test/log
GET /v1/test/mem
GET /v1/test/redis
GET /v1/test/snowflake
POST /v1/accounts/variant-async
POST /v1/accounts/variant-sync
POST /v1/dcrypt
POST /v1/encrypt
POST /v1/generateKeys
POST /v1/neo/raw
POST /v1/test/cryptodecrypt
POST /v1/test/cryptoencrypt
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: 5733ddf49ff49cd1f3d88d60d2f110e081615d2789e201ff24845cf66d5f1ebe
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /v1/cinema/country/{country}/cinemasWithGate
GET /v1/externalbooking/externalBookingId/{id}
POST /v1/externalbooking/Privatization/ListbyCinemas
POST /v1/externalbooking/add
POST /v1/externalbooking/cinemas/{cinemaId}/cancel
POST /v1/externalbooking/externalBookingId/{Id}/delete
POST /v1/externalbooking/externalBookingId/{id}/update
POST /v1/externalbookinguser/add
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: 5733ddf49ff49cd1aad035493b3b73504d58962b5567fe97fb9d7cf8e4aedd96
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /
GET /v1/accounts
GET /v1/accounts/dapper
GET /v1/accounts/dapper/proc/{id}
GET /v1/accounts/dapper/{id}
GET /v1/accounts/odata
GET /v1/accounts/{id}
GET /v1/accounts/{id}/variant-async
GET /v1/accounts/{id}/variant-sync
GET /v1/accountstable
GET /v1/clients
GET /v1/publish
GET /v1/subscribe
GET /v1/test/context
GET /v1/test/di
GET /v1/test/httpcall
GET /v1/test/log
GET /v1/test/mem
GET /v1/test/redis
GET /v1/test/snowflake
POST /v1/accounts/variant-async
POST /v1/accounts/variant-sync
POST /v1/dcrypt
POST /v1/encrypt
POST /v1/generateKeys
POST /v1/neo/raw
POST /v1/test/cryptodecrypt
POST /v1/test/cryptoencrypt