Detect mailcap.findmatch pickle payloads - #69
Open
massy-o wants to merge 1 commit into
Open
Conversation
massy-o
commented
May 14, 2026
massy-o
commented
May 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mailcap.findmatchas a dangerous pickle globalmailcap.findmatchWhy
mailcap.findmatchcan execute a matching mailcap entrytestcommand viaos.system(). Treating it as suspicious only leaves CLI scans with zero dangerous globals and exit code 0.Testing
uv run --with-editable . --with pytest --with numpy --with py7zr pytest tests/test_scanner.py::test_scan_pickle_bytes_flags_mailcap_findmatch tests/test_scanner.py::test_scan_pickle_bytes