Committed entrypoints run the Flask debug server on 0.0.0.0

[tg12]

Summary

WireTapper is wired to run the Flask development server with debug=True and host='0.0.0.0', which is an unsafe runtime posture for a network-facing reconnaissance application.

Evidence

• Remote source: https://github.com/h9zdev/WireTapper/blob/main/app.py#L496-L497
  • The main entrypoint runs app.run(host="0.0.0.0", port=8080, debug=True).
• Remote source: https://github.com/h9zdev/WireTapper/blob/main/app-env.py#L558-L559
  • The alternate entrypoint does the same.

Why this matters

• The Flask development server is not a production server.
• debug=True increases risk of sensitive error disclosure and unsafe runtime behavior if exposed outside tightly controlled local development.
• For an app that already proxies reconnaissance-style provider traffic, development-server deployment is an especially weak operational baseline.

Attack or failure scenario

An operator runs the repository as documented or copies the default entrypoint into a shared environment. The app binds on all interfaces under the Flask dev server with debug enabled. An exception path exposes detailed trace information, and the service lacks the hardening and process model expected of a production-facing web application.

Root cause

Development-runtime settings are committed directly in the executable entrypoints instead of being isolated behind an explicit development-only launch path.

Recommended fix

1. Remove debug=True from committed runtime entrypoints.
2. Do not use app.run(...) as the production launch contract.
3. Provide a proper WSGI/ASGI deployment path and separate dev launcher.
4. Make debug mode opt-in through environment-gated local development only.

Acceptance criteria

• Default entrypoints do not enable Flask debug mode.
• Production or shared deployment instructions use a real application server, not the Flask dev server.
• Debug mode is isolated to explicit local development configuration.
• Error responses in shared environments do not expose debug trace detail.

Suggested labels

• security
• devops
• production-readiness
• reliability

Priority

P1 (High)

Severity

High — network-facing recon application shipped with Flask debug server semantics in committed entrypoints.

Confidence

Confirmed — both committed entrypoints explicitly enable debug mode while binding on all interfaces.