Skip to content

πŸ›‘οΈ Sentinel: [HIGH] Fix missing serialization sinks in taint propagation - #175

Open
tachyon-beep wants to merge 2 commits into
mainfrom
sentinel-deserialization-sinks-14853706601299534012
Open

πŸ›‘οΈ Sentinel: [HIGH] Fix missing serialization sinks in taint propagation#175
tachyon-beep wants to merge 2 commits into
mainfrom
sentinel-deserialization-sinks-14853706601299534012

Conversation

@tachyon-beep

Copy link
Copy Markdown
Collaborator

🚨 Severity: HIGH
πŸ’‘ Vulnerability: dill.load, jsonpickle.decode, shelve.open, joblib.load, and torch.load were missing from _SERIALISATION_SINKS, which could lead to false negatives where untrusted data flows into these dangerous deserialization functions without losing its validation provenance.
🎯 Impact: If exploited, these false negatives could allow critical remote code execution vulnerabilities to slip through static analysis without alerting developers.
πŸ”§ Fix: Added "shelve.open", "dill.load", "dill.loads", "jsonpickle.decode", "joblib.load", and "torch.load" to _SERIALISATION_SINKS in src/wardline/scanner/taint/variable_level.py to ensure proper taint shedding.
βœ… Verification: Run uv run pytest to ensure all tests pass and ensure no regressions.


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

Added `shelve.open`, `dill.load`, `dill.loads`, `jsonpickle.decode`,
`joblib.load`, and `torch.load` to `_SERIALISATION_SINKS` in
`src/wardline/scanner/taint/variable_level.py`. This ensures that validation
provenance is properly shed and outputs from these deserialization calls are
treated as UNKNOWN_RAW, preventing false negatives in static analysis.

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.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
πŸ“ Code Review βœ… Completed 2026-08-31T16:43:17.032573Z bec14e3 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with πŸ‘€ while any review is running, comments if it has suggestions, and reacts with πŸ‘ once all reviews finish with no findings.

@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: bec14e3d87

ℹ️ 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".

"tomllib.load",
"tomli_w.dumps",
"tomli_w.dump",
"shelve.open",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Exempt newly created shelves from raw-source taint

When shelve.open(..., flag="n") is used, the underlying database is always created empty rather than opened for reading existing serialized data. Classifying every shelve.open result as UNKNOWN_RAW therefore taints a fresh shelf and all subsequent reads even when the program stores only clean values, producing false trusted-return or downstream-sink findings. Handle the literal fresh-create mode separately instead of applying this unconditional entry.

Useful? React with πŸ‘Β / πŸ‘Ž.

Added `shelve.open`, `dill.load`, `dill.loads`, `jsonpickle.decode`,
`joblib.load`, and `torch.load` to `_SERIALISATION_SINKS` in
`src/wardline/scanner/taint/variable_level.py`. This ensures that validation
provenance is properly shed and outputs from these deserialization calls are
treated as UNKNOWN_RAW, preventing false negatives in static analysis.

Also includes standard ruff formatting on the codebase to satisfy the format
checker which broke in CI due to existing unformatted files.

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