Skip to content

πŸ›‘οΈ Sentinel: [CRITICAL] Fix API key leak in streaming dictation#4

Open
euxaristia wants to merge 1 commit into
mainfrom
sentinel-fix-streaming-secrets-leak-13047065217895425372
Open

πŸ›‘οΈ Sentinel: [CRITICAL] Fix API key leak in streaming dictation#4
euxaristia wants to merge 1 commit into
mainfrom
sentinel-fix-streaming-secrets-leak-13047065217895425372

Conversation

@euxaristia

Copy link
Copy Markdown
Owner

πŸ›‘οΈ Sentinel: [CRITICAL] Fix API key leak in streaming dictation

🚨 Severity: CRITICAL
πŸ’‘ Vulnerability: Streaming dictation (Deepgram, OpenAI Realtime) did not redact API keys from connection errors or websocket payload error responses.
🎯 Impact: API keys injected into streaming websocket URLs or headers could be leaked in logs or outputs when transport-level errors occur or when the server responds with a typed error payload echoing the key.
πŸ”§ Fix: Applied providerio.Redact around all error endpoints and websocket error returns for Deepgram and OpenAI Realtime transcribers. Changed fmt.Errorf format specifier from %w to %s to prevent leaking the unredacted error via errors.Unwrap().
βœ… Verification: Ran go test ./internal/dictation/... and make lint.


PR created automatically by Jules for task 13047065217895425372 started by @euxaristia

🚨 Severity: CRITICAL
πŸ’‘ Vulnerability: Streaming dictation (Deepgram, OpenAI Realtime) did not redact API keys from connection errors or websocket payload error responses.
🎯 Impact: API keys injected into streaming websocket URLs or headers could be leaked in logs or outputs when transport-level errors occur or when the server responds with a typed error payload echoing the key.
πŸ”§ Fix: Applied `providerio.Redact` around all error endpoints and websocket error returns for Deepgram and OpenAI Realtime transcribers. Changed `fmt.Errorf` format specifier from `%w` to `%s` to prevent leaking the unredacted error via `errors.Unwrap()`.
βœ… Verification: Ran `go test ./internal/dictation/...` and `make lint`.

Co-authored-by: euxaristia <25621994+euxaristia@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

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

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@euxaristia, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
βš™οΈ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8b37943f-6a54-4294-9a07-c1c3441f0509

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 6fc1220 and c62da72.

πŸ“’ Files selected for processing (4)
  • .jules/sentinel.md
  • internal/dictation/transcriber_deepgram.go
  • internal/dictation/transcriber_openai_realtime.go
  • internal/dictation/transcriber_stream_test.go
✨ Finishing Touches
πŸ§ͺ Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch sentinel-fix-streaming-secrets-leak-13047065217895425372

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.

@github-actions

Copy link
Copy Markdown

Zero automated PR review

Verdict: No blockers found

Blockers

  • None found.

Validation

  • [pass] Diff hygiene: git diff --check
  • [pass] Tests: go test ./...
  • [pass] Build: go run ./cmd/zero-release build
  • [pass] Smoke build: go run ./cmd/zero-release smoke

Scope

Head: c62da72f4f41
Changed files (4): .jules/sentinel.md, internal/dictation/transcriber_deepgram.go, internal/dictation/transcriber_openai_realtime.go, internal/dictation/transcriber_stream_test.go

This deterministic review checks validation status and basic diff hygiene. A human reviewer still owns product judgment and design quality.

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