🔒 Fix SQL injection vectors via whitelist validation#998
Conversation
Co-authored-by: marko1olo <96879250+marko1olo@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. |
🎯 What: Hardcoded SQL expressions susceptible to injection via table names
⚠️ Risk: Medium risk B608 warnings raised by bandit and actual vulnerability if unchecked inputs reach query format strings
🛡️ Solution: Implemented a rigorous module-level whitelist validator that verifies table and column names exist in sqlite_master and strictly match an alphanumeric regex prior to query execution. Resolved false-positive Bandit warnings using inline nosec comments.
PR created automatically by Jules for task 13191043751284355727 started by @marko1olo