GHSA-22gh-3r9q-xf38

Source

https://github.com/advisories/GHSA-22gh-3r9q-xf38

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/09/GHSA-22gh-3r9q-xf38/GHSA-22gh-3r9q-xf38.json

JSON Data

https://api.test.osv.dev/v1/vulns/GHSA-22gh-3r9q-xf38

Aliases

Published

2021-09-20T19:53:30Z

Modified

2024-10-01T19:35:50.789061Z

Severity

8.1 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
9.3 (Critical) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CVSS Calculator

Summary

Lacking Protection against HTTP Request Smuggling in mitmproxy

Details

Impact

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 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 you use mitmproxy to protect an HTTP/1 service, no action is required.

Patches

The vulnerability has been fixed in mitmproxy 7.0.3 and above.

Acknowledgements

We thank João Sobral (@chinchila) for responsibly disclosing this vulnerability to the mitmproxy team.

Timeline

2021-09-08: Received initial report for mitmproxy <= 6.0.2.
2021-09-08: Requested clarification if 7.x is affected.
2021-09-10: Received additional details, 7.x situation still unclear.
2021-09-13: Internally determined that 7.x is also affected.
2021-09-13: Shared initial fix with researcher.
2021-09-14: Received confirmation that fix is working, but H2.TE/H2.CL should also be looked at.
2021-09-14: Shared revised fix that includes additional H2.TE mitigations.
2021-09-14: Received confirmation that revised fix is working.
2021-09-16: Completed internal patch review.
2021-09-16: Published patch release and advisory.

Database specific

{
    "nvd_published_at": "2021-09-16T15:15:00Z",
    "cwe_ids": [
        "CWE-444"
    ],
    "severity": "CRITICAL",
    "github_reviewed": true,
    "github_reviewed_at": "2021-09-17T18:30:53Z"
}

References

Affected packages

PyPI / mitmproxy

Package

Name: mitmproxy; View open source insights on deps.dev
Purl: pkg:pypi/mitmproxy

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

7.0.3

Affected versions

0.*

0.8

0.8.1

0.9

0.9.1

0.9.2

0.10

0.10.1

0.11

0.11.1

0.11.2

0.11.3

0.12.0

0.12.1

0.13

0.14.0

0.15

0.16

0.17

0.18.1

0.18.2

0.18.3

1.*

1.0.0

1.0.1

1.0.2

2.*

2.0.0

2.0.1

2.0.2

3.*

3.0.0

3.0.1

3.0.2

3.0.3

3.0.4

4.*

4.0.0

4.0.1

4.0.3

4.0.4

5.*

5.0.0

5.0.1

5.1.0

5.1.1

5.2

5.3.0

6.*

6.0.0

6.0.1

6.0.2

7.*

7.0.0

7.0.1

7.0.2