Skip to content

πŸ›‘οΈ Sentinel: [security improvement] Improve CensorWriter log regex#248

Draft
arumes31 wants to merge 1 commit into
mainfrom
sentinel/censor-log-regex-fix-9251810033178029496
Draft

πŸ›‘οΈ Sentinel: [security improvement] Improve CensorWriter log regex#248
arumes31 wants to merge 1 commit into
mainfrom
sentinel/censor-log-regex-fix-9251810033178029496

Conversation

@arumes31
Copy link
Copy Markdown
Owner

@arumes31 arumes31 commented Jun 7, 2026

πŸ›‘οΈ Sentinel: [security improvement]

🚨 Severity: LOW / MEDIUM
πŸ’‘ Vulnerability: The log censor regex failed to catch keys mapped using the = character and could be prone to false positives.
🎯 Impact: Sensitive fields formatted as token=123 might leak into application logs. Additionally, false positives might inadvertently censor valid log text.
πŸ”§ Fix: Refined censorRE to explicitly match = assignments and tighten the separator requirements to [:=] or quoted tokens, avoiding general whitespace masking.
βœ… Verification: go test ./cmd/server/... confirms that all string formats, including = assignments and general plain text, are handled securely without false positives.


PR created automatically by Jules for task 9251810033178029496 started by @arumes31

This commit enhances the regex used by the application's `CensorWriter` to accurately mask sensitive fields. The previous regex (`["':\s]+`) did not capture the `=` operator, which is commonly used in token definitions and URL query parameters (e.g., `token=...`).

The updated regex `(?i)(password|secret|token)(["':\s=]*[:=][\s"':=]*|\s*["']\s*)([^"'\s,{}]+)` resolves this and also prevents false positives in regular text (e.g., "I have a secret base").

Changes:
- Refined `censorRE` in `cmd/server/main.go`
- Added comprehensive unit tests in `cmd/server/main_test.go` to test `=` assignment, partial matches, and false positives.

Co-authored-by: arumes31 <114224498+arumes31@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

πŸ‘‹ 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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 7, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

βš™οΈ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 10e5002d-17f7-4409-89d2-a8ebaafbe104

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • πŸ” Trigger review
✨ Finishing Touches
πŸ§ͺ Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch sentinel/censor-log-regex-fix-9251810033178029496

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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.

1 participant