Bump mitmproxy from 10.4.2 to 12.2.2 in /tests/zenko_tests#2390
Bump mitmproxy from 10.4.2 to 12.2.2 in /tests/zenko_tests#2390dependabot[bot] wants to merge 1 commit intodevelopment/2.14from
Conversation
Bumps [mitmproxy](https://github.com/mitmproxy/mitmproxy) from 10.4.2 to 12.2.2. - [Release notes](https://github.com/mitmproxy/mitmproxy/releases) - [Changelog](https://github.com/mitmproxy/mitmproxy/blob/main/CHANGELOG.md) - [Commits](mitmproxy/mitmproxy@v10.4.2...v12.2.2) --- updated-dependencies: - dependency-name: mitmproxy dependency-version: 12.2.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Hello dependabot[bot],My role is to assist you with the merge of this Available options
Available commands
Status report is not available. The following options are set: bypass_author_approval, bypass_jira_check |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: bypass_author_approval, bypass_jira_check |
There was a problem hiding this comment.
Dependency Bump Evaluation
Version change: mitmproxy 10.4.2 -> 12.2.2 (major, spanning two major versions)
Semver bump type: major
Changes (10.4.2 -> 12.2.2):
- Python 3.12+ now required (11.0.0)
- mitmproxy.dns.Message renamed to mitmproxy.dns.DNSMessage (11.0.0)
- Filter expressions case-insensitive by default (11.1.0)
- Contentview API overhauled - returns plain str instead of previous types (12.0.0)
- server_replay_nopop option renamed to server_replay_reuse (12.0.0)
- htpasswd parser now only supports bcrypt and SHA-1 (12.2.0)
- Security fix: LDAP injection vulnerability GHSA-527g-3w9m-29hv (12.2.2)
Breaking changes: Multiple across two major versions (see above), but none affect this codebase.
Security concerns: 12.2.2 fixes an LDAP injection vulnerability (GHSA-527g-3w9m-29hv). Upgrading is recommended.
Impact on codebase: mitmproxy is listed in tests/zenko_tests/requirements.txt and installed via pip3 install in configure-e2e.sh, but no Python file in the test suite imports or references mitmproxy. The dependency appears unused. All identified breaking changes (DNS API rename, contentview API, option renames, htpasswd parser, filter behavior) have zero impact since none of these APIs are consumed.
Recommendation: SAFE TO MERGE
Notes: Consider removing mitmproxy from requirements.txt entirely if it is confirmed to be an unused dependency - this would reduce install time and attack surface.
— Claude Code
Bumps mitmproxy from 10.4.2 to 12.2.2.
Release notes
Sourced from mitmproxy's releases.
... (truncated)
Changelog
Sourced from mitmproxy's changelog.
... (truncated)
Commits
437fb75mitmproxy 12.2.27458ea2remove codacy badged835965Update CHANGELOG.md71c9234Fix LDAP Sanitization (#8178)cc58fc9load pending scripts before dumping options (#8176)bf16594SECURITY.md: Exclude DoS from scope (#8171)6d1f71ecorrect a parameter (#8172)d1e06b6Fix uppercase scheme (#8174)e0840a6Fix console command panel losing focus due to incoming traffic (#8173)ca58cd8fix: display failed CONNECT requests in mitmdump (#8175)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.