π‘οΈ Sentinel: [MEDIUM] Fix Error Stack Trace Leakage - #81
Conversation
Co-authored-by: DerUntote <8378077+DerUntote@users.noreply.github.com>
|
π Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a π emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
π¨ Severity: MEDIUM
π‘ Vulnerability: Unhandled exceptions in bot commands appended the full
e.stacktrace to moderation log messages on Discord whenconfig.debugwas true, exposing server file paths and internal architecture.π― Impact: Malicious users could potentially exploit detailed knowledge of the internal architecture and server file paths if they gained access to the logs.
π§ Fix: Changed the error handling block in
bot/bot.jsto log the full stack trace internally usingconsole.errorinstead of sending it externally.β Verification: Ran syntax validation and manually reviewed the code to ensure stack traces are no longer added to
msgTxt.PR created automatically by Jules for task 12481100339616240628 started by @DerUntote