fix: block legacy httplib pickle aliases#703
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThe pickle scanner's security blocklist is expanded to treat legacy httplib module references as dangerous, equivalent to http.client. A single module addition to the dangerous modules list is accompanied by comprehensive test coverage validating httplib detection across various pickle payload scenarios including import-only globals, REDUCE operations, and multi-stream contexts. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
Summary
httplibpickle globals the same way as existinghttpandhttp.clientnetwork-danger module coveragehttp.client, and a safe stdlib negativeValidation
Summary by CodeRabbit