Repository navigation
docs(reports): add the mitmproxy 2026-10-02 analysis report - #213
Merged
Merged
Conversation
Qualified review of the 87 results of engine 0.21.0 with the enterprise plugins on mitmproxy be758251, with the raw findings, SBOM, VEX, line-by-line triage and the targeted verification of the Werkzeug safe_join scenario.
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
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
Add the qualified review of an analysis of mitmproxy (
be758251) with engine 0.21.0 (4365d6e) and the enterprise plugins (ac35460,[email protected]), underreports/mitmproxy-2026-10-02/:rapport.md(French): 87 results, 75 alerts and 12 coverage notes, qualified as 8 true positives (6 missing timeouts, conditional SHA-1 in htpasswd, Werkzeug 3.1.5 pinned), 66 false positives and 1 dual reading (thesafe_joincall is real, the Windows device-name scenario is neutralised by mitmproxy's per-segment join). No remote exploitation is shown.findings.json,sbom.json,vex.json,analysis.stderr: raw outputs of the scan, unmodified.triage.csv: verdict and verified position of every result.verification.txt: the targeted check of the Werkzeug scenario, against the official 3.1.5 wheel (SHA-256 matchinguv.lock). It is a simulation of Windows path semantics, not a native reproduction; the report keeps the generated VEX statusaffected.The engine defects found during the review are tracked in #206 to #211 and listed in the report; their effect is to be measured by a new scan with the same parameters.
Validation
findings.json.be758251; no local absolute path remains inrapport.mdortriage.csv.findings.jsonkeeps the absoluterootandsyntax-errormessages as the engine produced them.git diff --checkclean. No source or test file changed.