Add Swagger / OpenAPI / Redoc paths to dir_wordlist (#1378)#1542
Add Swagger / OpenAPI / Redoc paths to dir_wordlist (#1378)#1542ChrisJr404 wants to merge 1 commit into
Conversation
Closes #1378. Swagger / OpenAPI documentation is currently only detected through passive technology fingerprinting in web_technologies.yaml (matching swagger-ui-bundle.js in response bodies), which leaves the active recon path blind to the dozens of well-known endpoints applications expose by default - exactly what the issue calls out. This change appends 28 new paths to nettacker/lib/payloads/wordlists/ dir_wordlist.txt so the dir_scan / config_scan modules can probe for exposed API documentation: - Swagger UI variants: swagger, swagger/, swagger-ui, swagger-ui/, swagger-ui.html, swagger-ui/index.html - Swagger spec files: swagger.json / .yaml / .yml plus the versioned swagger/v1/swagger.json and swagger/v2/swagger.json patterns used by ASP.NET Core and Swagger-Codegen - api-docs family: api-docs, api-docs/, api/swagger, api/swagger.json, api/swagger-ui.html, v2/api-docs, v3/api-docs (springdoc / springfox) - OpenAPI 3 specs: openapi, openapi.json, openapi.yaml, openapi.yml, api/openapi.json, api/openapi.yaml (FastAPI, Connexion, Smithy) - Redoc + dev-only routes: redoc, docs/swagger, docs/api, docs/openapi.json These endpoints can leak full API schemas and unauthenticated routes, so adding them to the active wordlist materially improves Nettacker's API recon coverage for relatively no false-positive risk.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Summary by CodeRabbit
WalkthroughThe PR extends the directory wordlist with Swagger/OpenAPI endpoint variants commonly exposed during API reconnaissance. It adds 29 entries covering ChangesSwagger/OpenAPI Wordlist Expansion
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
|
The linked issue must be assigned to the PR author. |
Summary
Closes #1378.
Nettacker currently only detects Swagger / OpenAPI passively through technology fingerprinting in `web_technologies.yaml` (matching `swagger-ui-bundle.js` in response bodies). That leaves the active recon path blind to the dozens of well-known endpoints applications expose by default — exactly what the issue describes.
This MR appends 28 new paths to `nettacker/lib/payloads/wordlists/dir_wordlist.txt` so the `dir_scan` / `config_scan` modules can actively probe for exposed API documentation.
Paths added
These endpoints frequently expose full API schemas and unauthenticated routes, so adding them to the active wordlist materially improves Nettacker's API recon coverage with no false-positive risk (404 responses are still 404s).
Diff
29 net new lines (one was already a deduplicated entry on the existing trailing-line write).
Test plan