[Tracking] Gateway security & robustness hardening — 5 tasks (#4769–#4773)

[larsspinetta12]

Summary

Tracking issue for a batch of 5 gateway security & robustness hardening tasks surfaced during Phase 1A review. Grouped here as sub-issues for visibility; they are otherwise independent and parallelizable — no hard blocking chain.

Tasks

• [BUG] Telegram gateway poller can log/return a live bot token on transient failures #4769 — Telegram gateway poller can log/return a live bot token (S · security)
• [BUG] Body-size cap only on /alerts; /investigate and /api/investigations buffer unbounded JSON #4770 — Body-size cap only on /alerts; other routes buffer unbounded JSON (M · security/reliability)
• [BUG] Slack attachment download has no host allowlist (Discord's downloader does) #4771 — Slack attachment download follows redirects with bot token, no host allowlist (M · security)
• [BUG] S3 upload and Postgres connect have no bounded timeout — can hang gateway threads #4772 — S3 upload & Postgres connect have no bounded timeout (S · reliability)
• [BUG] Credits client logs full exception (may echo webapp URL) on unreachable path #4773 — Credits client logs full exception on unreachable path (XS · good first issue)

Notes

• Soft ordering only: [BUG] Credits client logs full exception (may echo webapp URL) on unreachable path #4773 is the smallest and establishes the "log type(exc).__name__, not raw str(exc)" hygiene that [BUG] Telegram gateway poller can log/return a live bot token on transient failures #4769 also applies — doing [BUG] Credits client logs full exception (may echo webapp URL) on unreachable path #4773 first sets a reusable pattern, but it does not block the others.
• Security-class items ([BUG] Telegram gateway poller can log/return a live bot token on transient failures #4769, [BUG] Slack attachment download has no host allowlist (Discord's downloader does) #4771): keep exploit specifics light; route anything actively exploitable through the repo Security Policy.

[DevSars24]

Hi @Davidson3556

I'd like to work on one of the issues in this tracking batch.

If it's okay, I'd be happy to start with #4773 (Credits client logs full exception on unreachable path) since it looks like a good first step and establishes the logging pattern mentioned in the tracking issue. If that's already taken, I'm also interested in #4769 or any other unassigned task from this batch.

Please let me know which one you'd prefer me to work on. Thanks!

[Nikunjsaini07]

Hi @Davidson3556,

I'd like to take on #4772 if it's available.

I've reviewed the issue and would be happy to investigate the relevant code paths, implement a fix for the missing bounded timeouts, and submit a PR.

If it's available, could you please assign it to me?

Thanks