Skip to content

πŸ”’ Fix ReDoS vulnerability in read_secrets security rule#87

Open
google-labs-jules[bot] wants to merge 1 commit into
mainfrom
fix-security-guard-redos-7366585897842753865
Open

πŸ”’ Fix ReDoS vulnerability in read_secrets security rule#87
google-labs-jules[bot] wants to merge 1 commit into
mainfrom
fix-security-guard-redos-7366585897842753865

Conversation

@google-labs-jules

Copy link
Copy Markdown

🎯 What: Fixed a catastrophic ReDoS (Regular Expression Denial of Service) vulnerability in the read_secrets rule of the security_guard hook.
⚠️ Risk: A long shell command argument could cause the naive .* regex to backtrack extensively, leading to a denial of service (CPU exhaustion) against the agent.
πŸ›‘οΈ Solution: Removed the vulnerable regex pattern and introduced a custom _is_reading_secrets check function. This relies on the robust _split_subcommands and _shell_split logic to properly identify the executable in position and validate if trailing arguments match secret files without resorting to unbounded lookaheads.


PR created automatically by Jules for task 7366585897842753865 started by @zknpr

The previous regular expression for the `read_secrets` rule
in `hooks/security_guard.py` used `.*` which was vulnerable
to catastrophic backtracking (ReDoS) when processing long command
arguments.

This commit replaces the vulnerable pattern with a custom programmatic
`check` parser (`_is_reading_secrets`). It properly tokenizes the
shell command using existing `_split_subcommands` and `_shell_split`
functions, identifying the command and testing specific target arguments
safely, mitigating the denial of service risk.
@google-labs-jules

Copy link
Copy Markdown
Author

πŸ‘‹ 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants