🔒 Fix SQL injection vulnerabilities in Quiz_4.py - #39
Conversation
Co-authored-by: tsainez <13399044+tsainez@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: Fixed SQL Injection vulnerabilities in
⚠️ Risk: The previous implementation used string
insertPC,updatePrinter, anddeleteLaptopfunctions withinpython/Quiz_4.py..format()to construct SQL queries, allowing a malicious actor to inject arbitrary SQL statements if user inputs were unescaped, potentially leading to unauthorized data manipulation or deletion.🛡️ Solution: Refactored the
cursor.executestatements to use parameterized queries (?), ensuring that inputs are safely treated as values rather than executable code. Also introducedtest_quiz_4.pywith an in-memory SQLite setup to verify the functionality of these database modifications.PR created automatically by Jules for task 6505424191946188987 started by @tsainez