mitmproxy - Debian Package Tracker

general

source: mitmproxy (main)
version: 6.0.2-1
maintainer: Debian Python Team (DMD)
uploaders: Sebastien Delafond [DMD] – Andrej Shadura [DMD]
arch: all
std-ver: 4.4.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 0.18.2-6+deb9u2
oldstable: 4.0.4-5
stable: 6.0.2-1
testing: 6.0.2-1
unstable: 6.0.2-1

versioned links

0.18.2-6+deb9u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.0.4-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
6.0.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

mitmproxy (2 bugs: 0, 1, 1, 0)

action needed

Problems while searching for a new upstream version high

uscan had problems while searching for a new upstream version:

unknown protocol for LWP: pgpmode=none

Created: 2020-06-29 Last update: 2022-08-11 17:04

A new upstream version is available: 8.1.1 high

A new upstream version 8.1.1 is available, you should consider packaging it.

Created: 2022-07-02 Last update: 2022-08-11 17:04

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2021-39214: mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.2 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While a smuggled request is still captured as part of another request's body, it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless one uses mitmproxy to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 7.0.3 and above.
CVE-2022-24766: mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.4 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless mitmproxy is used to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 8.0.0 and above. There are currently no known workarounds.

Created: 2022-07-04 Last update: 2022-08-01 13:40

2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:

CVE-2021-39214: mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.2 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While a smuggled request is still captured as part of another request's body, it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless one uses mitmproxy to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 7.0.3 and above.
CVE-2022-24766: mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.4 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless mitmproxy is used to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 8.0.0 and above. There are currently no known workarounds.

Created: 2022-07-04 Last update: 2022-08-01 13:40

lintian reports 4 errors and 14 warnings high

Lintian reports 4 errors and 14 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2021-01-27 Last update: 2022-07-30 12:15

1 new commit since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 350c5a0d304c1c88c531c7b734eb6cd18e77cd00
Author: Sébastien Delafond <sdelafond@gmail.com>
Date:   Fri Sep 17 06:41:10 2021 +0200

    Remove myself from Uploaders

Created: 2021-09-18 Last update: 2022-08-07 20:35

2 low-priority security issues in bullseye low

There are 2 open security issues in bullseye.

2 issues left for the package maintainer to handle:

CVE-2021-39214: (needs triaging) mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.2 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While a smuggled request is still captured as part of another request's body, it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless one uses mitmproxy to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 7.0.3 and above.
CVE-2022-24766: (needs triaging) mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.4 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless mitmproxy is used to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 8.0.0 and above. There are currently no known workarounds.

You can find information about how to handle these issues in the security team's documentation.

Created: 2022-07-04 Last update: 2022-08-01 13:40

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.1 instead of 4.4.0).

Created: 2019-07-08 Last update: 2022-05-11 23:25

news

[rss feed]

[2021-01-09] mitmproxy 6.0.2-1 MIGRATED to testing (Debian testing watch)
[2021-01-06] Accepted mitmproxy 6.0.2-1 (source) into unstable (Andrej Shadura) (signed by: Andrew Shadura)
[2021-01-04] Accepted mitmproxy 5.3.0-3 (source) into unstable (Andrej Shadura) (signed by: Andrew Shadura)
[2021-01-04] mitmproxy 5.3.0-2 MIGRATED to testing (Debian testing watch)
[2020-12-30] Accepted mitmproxy 5.3.0-2 (source) into unstable (Andrej Shadura) (signed by: Andrew Shadura)
[2020-12-06] mitmproxy 5.3.0-1 MIGRATED to testing (Debian testing watch)
[2020-11-30] Accepted mitmproxy 5.3.0-1 (source) into unstable (Andrej Shadura) (signed by: Andrew Shadura)
[2020-07-05] mitmproxy 5.1.1-2 MIGRATED to testing (Debian testing watch)
[2020-06-29] Accepted mitmproxy 5.1.1-2 (source) into unstable (Andrej Shadura) (signed by: Andrew Shadura)
[2020-06-19] Accepted mitmproxy 5.1.1-1 (source) into unstable (Andrej Shadura) (signed by: Andrew Shadura)
[2020-06-18] mitmproxy REMOVED from testing (Debian testing watch)
[2020-04-14] mitmproxy 4.0.4-6.1 MIGRATED to testing (Debian testing watch)
[2020-04-08] Accepted mitmproxy 4.0.4-6.1 (source) into unstable (Andrej Shadura) (signed by: Andrew Shadura)
[2020-02-19] mitmproxy REMOVED from testing (Debian testing watch)
[2019-08-30] Accepted mitmproxy 0.18.2-6+deb9u2 (source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Sebastien Delafond)
[2019-08-25] Accepted mitmproxy 0.18.2-6+deb9u1 (source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Sebastien Delafond)
[2019-07-09] mitmproxy 4.0.4-6 MIGRATED to testing (Debian testing watch)
[2019-05-23] Accepted mitmproxy 4.0.4-6 (source) into unstable (Sebastien Delafond)
[2019-04-02] mitmproxy 4.0.4-5 MIGRATED to testing (Debian testing watch)
[2019-03-04] Accepted mitmproxy 4.0.4-5 (source) into unstable (Sebastien Delafond)
[2018-09-05] mitmproxy 4.0.4-4 MIGRATED to testing (Debian testing watch)
[2018-08-30] Accepted mitmproxy 4.0.4-4 (source) into unstable (Sebastien Delafond)
[2018-08-12] mitmproxy 4.0.4-3 MIGRATED to testing (Debian testing watch)
[2018-08-06] Accepted mitmproxy 4.0.4-3 (source) into unstable (Sebastien Delafond)
[2018-08-06] Accepted mitmproxy 4.0.4-2 (source) into unstable (Sebastien Delafond)
[2018-08-05] Accepted mitmproxy 4.0.4-1 (source) into unstable (Sebastien Delafond)
[2018-08-05] Accepted mitmproxy 3.0.4-1 (source) into unstable (Sebastien Delafond)
[2018-04-08] mitmproxy 3.0.3-1 MIGRATED to testing (Debian testing watch)
[2018-04-02] Accepted mitmproxy 3.0.3-1 (source) into unstable (Sebastien Delafond)
[2018-03-24] mitmproxy 2.0.2-4 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 5
RC: 0
I&N: 4
M&W: 1
F&P: 0
patch: 0

links

homepage
lintian (4, 14)
buildd: logs, clang, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
screenshots

ubuntu

[Information about Ubuntu for Debian Developers]

version: 6.0.2-1
1 bug