Skip to content

🛡️ Sentinel: [HIGH] Fix untrusted data leakage in default parameter evaluation - #162

Open
tachyon-beep wants to merge 1 commit into
mainfrom
sentinel/fix-default-param-taint-16587914181932198151
Open

🛡️ Sentinel: [HIGH] Fix untrusted data leakage in default parameter evaluation#162
tachyon-beep wants to merge 1 commit into
mainfrom
sentinel/fix-default-param-taint-16587914181932198151

Conversation

@tachyon-beep

Copy link
Copy Markdown
Collaborator

🚨 Severity: HIGH
💡 Vulnerability: Default parameter expressions in the L2 taint analysis (_seed_parameters) were evaluated using the function_taint. This allowed untrusted data state to leak into the default parameter's AST evaluation context for @trusted functions.
🎯 Impact: False positives could occur, and the taint state of default parameters could incorrectly assume an untrusted state instead of reflecting the actual definition-time values.
🔧 Fix: Modified _seed_parameters in src/wardline/scanner/taint/variable_level.py to evaluate default parameter expressions using TaintState.INTEGRAL instead of function_taint.
✅ Verification: Tests run via make test, typechecks pass via make typecheck, and golden identity tests regenerated successfully.


PR created automatically by Jules for task 16587914181932198151 started by @tachyon-beep

Default parameters in Python are evaluated at function definition time,
but `_seed_parameters` was incorrectly evaluating their AST nodes with the
`function_taint` instead of a clean `TaintState.INTEGRAL`. This caused
untrusted data to bleed into `@trusted` functions' default parameter analysis.
This fix updates the L2 taint analysis to correctly model definition-time evaluation.

Co-authored-by: tachyon-beep <544926+tachyon-beep@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.

Copilot AI lite review requested due to automatic review settings August 24, 2026 16:44

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3e0b57b25e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

if 0 <= param_idx < len(all_pos_params):
param_name = all_pos_params[param_idx].arg
default_taints[param_name] = _resolve_expr(default_expr, function_taint, taint_map or {}, {})
default_taints[param_name] = _resolve_expr(default_expr, TaintState.INTEGRAL, taint_map or {}, {})

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep unresolved default expressions conservatively tainted

When a default contains an unresolved name or bare call that is absent from taint_map (for example, a dynamically bound factory or module value), _resolve_expr uses this argument as its fallback. Passing INTEGRAL therefore marks the expression provably clean even though definition-time evaluation does not imply trustworthy data and no enclosing definition-scope taint is supplied here. If the argument is omitted, the clean default seed can suppress sink or trusted-return findings for attacker-controlled defaults; resolve against the definition scope when available or retain a conservative raw/unknown fallback rather than INTEGRAL.

Useful? React with 👍 / 👎.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates L2 taint analysis for default parameter evaluation to avoid inheriting call-time function taint.

Changes:

  • Uses an integral baseline for positional and keyword-only defaults.
  • Updates Sentinel documentation and identity metadata.
  • Applies formatting changes across MCP, install, and test files.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file
File Summary
tests/unit/mcp/test_server_trust_grants.py Formatting cleanup.
tests/unit/install/test_mcp_json.py Formatting cleanup.
tests/unit/install/test_doctor_pack_grants.py Formatting cleanup.
tests/golden/identity/corpus/META.json Updates regeneration metadata.
src/wardline/scanner/taint/variable_level.py Changes default taint seeding. Moderate findings remain regarding definition-time scope taints and missing regression coverage.
src/wardline/mcp/server.py Formatting cleanup.
src/wardline/install/block.py Spacing cleanup.
.jules/sentinel.md Documents the vulnerability and prevention.
Suppressed comments (1)

src/wardline/scanner/taint/variable_level.py:822

  • Keyword-only defaults have the same gap: a raw module global used in def f(*, value=RAW) is resolved against {} as INTEGRAL before the synthetic global seed is applied, so a trusted sink can miss the raw value. Apply the same definition-scope taint handling here.
            default_taints[param.arg] = _resolve_expr(kw_default_expr, TaintState.INTEGRAL, taint_map or {}, {})

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

if 0 <= param_idx < len(all_pos_params):
param_name = all_pos_params[param_idx].arg
default_taints[param_name] = _resolve_expr(default_expr, function_taint, taint_map or {}, {})
default_taints[param_name] = _resolve_expr(default_expr, TaintState.INTEGRAL, taint_map or {}, {})
if 0 <= param_idx < len(all_pos_params):
param_name = all_pos_params[param_idx].arg
default_taints[param_name] = _resolve_expr(default_expr, function_taint, taint_map or {}, {})
default_taints[param_name] = _resolve_expr(default_expr, TaintState.INTEGRAL, taint_map or {}, {})
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.

2 participants