Skip to content

🛡️ Sentinel: [CRITICAL] Remove Public Debug Endpoint Exposing Environment Variables #119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
GerryK97 wants to merge 1 commit into
base: Production
Choose a base branch
from
Open

🛡️ Sentinel: [CRITICAL] Remove Public Debug Endpoint Exposing Environment Variables #119

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .jules/sentinel.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
## 2024-05-15 - Information Exposure via Public Debug Endpoint
**Vulnerability:** A public debug endpoint (`/debug`) was exposing sensitive environment variables, including `MONGODB_URI` (truncated but still leaking the password and cluster info) and `NEXTAUTH_URL`.
**Learning:** Even partial exposure of connection strings (e.g., using `substring(0, 60)`) can leak sensitive authentication material like passwords. Furthermore, debug endpoints intended for local development should never be accessible without authentication or deployed to production.
**Prevention:** Remove or strictly authenticate and authorize debug routes. Never expose environment variables or connection strings, even partially, in API responses. Use internal logging instead of public-facing endpoints for debugging configuration issues.
100 changes: 0 additions & 100 deletions src/app/debug/route.ts
View file
Open in desktop

This file was deleted.