🔒 Fix unsafe CSV deserialization by removing engine="python"#53
🔒 Fix unsafe CSV deserialization by removing engine="python"#53derrynknife wants to merge 4 commits intomasterfrom
Conversation
Co-authored-by: derrynknife <18457108+derrynknife@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. |
Co-authored-by: derrynknife <18457108+derrynknife@users.noreply.github.com>
…cies Co-authored-by: derrynknife <18457108+derrynknife@users.noreply.github.com>
…lity Co-authored-by: derrynknife <18457108+derrynknife@users.noreply.github.com>
🎯 What: The
⚠️ Risk: The "python" engine for Pandas
pd.read_csvfunctions insurpyval/datasets/__init__.pywere usingengine="python", which can be vulnerable to unsafe CSV deserialization.read_csvhas historically had vulnerabilities or performance issues compared to the default "c" engine. Using it for data loading can expose users to unsafe execution if malicious CSVs are loaded.🛡️ Solution: Removed the
engine="python"argument from allpd.read_csvcalls in the dataset loading functions. The default "c" engine is safer, faster, and perfectly capable of handling these standard CSV datasets.PR created automatically by Jules for task 5198042484183905525 started by @derrynknife