fix: secure URL transcoding path traversal vulnerability in REST fallback - #3973
fix: secure URL transcoding path traversal vulnerability in REST fallback#3973danieljbruce wants to merge 1 commit into
Conversation
…back
Validate and percent-encode path parameters according to RFC 3986 and
the Cloud SDK URL transcoding design specification. Protect against path
traversal ('.' or '..') and parameter injection ('?', '#', '$').
Co-authored-by: danieljbruce <8935272+danieljbruce@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. |
1 participant
Implemented URL transcoding validation and strict RFC 3986 percent-encoding in generated REST API methods to prevent path traversal and parameter injection vulnerabilities.
PR created automatically by Jules for task 7994329598920679972 started by @danieljbruce