Skip to content

πŸ›‘οΈ Sentinel: [MEDIUM] Fix Environment Variable Leakage in Error Messages#261

Open
davidruzicka wants to merge 1 commit into
mainfrom
sentinel/fix-env-leakage-in-errors-17449932210096390122
Open

πŸ›‘οΈ Sentinel: [MEDIUM] Fix Environment Variable Leakage in Error Messages#261
davidruzicka wants to merge 1 commit into
mainfrom
sentinel/fix-env-leakage-in-errors-17449932210096390122

Conversation

@davidruzicka
Copy link
Copy Markdown
Owner

🚨 Severity: MEDIUM
πŸ’‘ Vulnerability: Error messages for environment variable configuration were echoing back the exact values passed in, which could potentially expose sensitive data if an environment variable was accidentally misconfigured with a secret value.
🎯 Impact: If exploited or accidentally triggered, sensitive environment variable content could be leaked in application logs or to clients interacting with the service API directly.
πŸ”§ Fix: Refactored multiple configuration parsing handlers to omit the raw user inputs inside thrown ConfigurationError messages.
βœ… Verification: Ran npm run test:unit and successfully passed tests. Additionally recorded this learning pattern in .jules/sentinel.md to prevent similar issues.


PR created automatically by Jules for task 17449932210096390122 started by @davidruzicka

This commit modifies the `ConfigurationError` messages in `src/automation/artifact-signing-config.ts`, `src/tool-filter/config/env-config-parser.ts`, and `src/mcp/mcp-server.ts` to no longer include the exact `raw` values extracted from environment variables.

If a user configured an application setting with a sensitive value (e.g. accidentally pasting an API key into `MCP4_AGENT_ARTIFACT_ALLOW_UNSIGNED`), previously the exact value could be echoed out as part of a validation failure and risk logging. This implements a more secure fail pattern by outputting generic validation guidance.

Co-authored-by: davidruzicka <14172985+davidruzicka@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.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 27, 2026

Codecov Report

βœ… All modified and coverable lines are covered by tests.
βœ… All tests successful. No failed tests found.

πŸ“’ Thoughts on this report? Let us know!

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