🔒 Prevent API key exposure in Census extractor error logs#40
🔒 Prevent API key exposure in Census extractor error logs#40Data-Science-Link wants to merge 1 commit into
Conversation
…osure Co-authored-by: Data-Science-Link <61164085+Data-Science-Link@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. |
🔒 Security Scan CompleteCode Security: ✅ Checked with Bandit All security checks passed! See Actions logs for details. |
🎯 What: Modified
census_extractor.pyto securely redact the Census API key from any exception strings before logging them, and reformatted the file withblack.requestsexceptions and log the stringified error which, forrequests.HTTPErroron a 4xx response, would include the fully-constructed URL including the API key in plaintext. This creates a data exposure vulnerability, leaking secrets into logs or CI/CD pipelines.🛡️ Solution: Added a
_redacthelper method inCensusExtractorthat safely replaces occurrences ofself.api_keywith***REDACTED***in error message strings before they are sent to the logger. Wrapped all 4 exception logging blocks with this redaction layer.PR created automatically by Jules for task 12606068584406796596 started by @Data-Science-Link