forked from LengKundee/MQL5-Google-Onedrive
15 lines
1.5 KiB
Markdown
15 lines
1.5 KiB
Markdown
# Sentinel's Journal
|
|
|
|
## 2026-02-07 - Telegram Bot Authorization Bypass
|
|
**Vulnerability:** The Telegram Deployment Bot (`scripts/telegram_deploy_bot.py`) contained a "Fail Open" vulnerability where omitting the `TELEGRAM_ALLOWED_USER_IDS` environment variable resulted in granting access to *all* Telegram users instead of *none*.
|
|
**Learning:** Security controls must default to deny (Fail Closed). Implicitly allowing access when configuration is missing creates silent vulnerabilities that are hard to detect until exploited.
|
|
**Prevention:** Ensure all authorization checks explicitly return `False` or throw an exception if the access control list is empty or undefined. Never default to `True` in security-critical paths.
|
|
|
|
## 2026-02-13 - [Documentation] Cloudflare Nameservers and Domain Unification
|
|
- Updated Cloudflare nameservers to daisy.ns.cloudflare.com and rocco.ns.cloudflare.com.
|
|
- Unified domain name to lengkundee01.org across CNAME and PWA documentation.
|
|
|
|
## 2026-02-14 - Information Leak via Error Messages
|
|
**Vulnerability:** The web dashboard (`scripts/web_dashboard.py`) exposed raw exception messages directly to users in 500 responses. This could leak internal details like file paths or stack traces.
|
|
**Learning:** Never return raw exception strings to users. Generic error messages ("Internal Server Error") should be shown to users while detailed errors are logged securely on the server.
|
|
**Prevention:** Catch all exceptions at the route level, log the details to stderr/logging, and return a sanitized, generic error message to the client.
|