Lynx through 2.8.9 mishandles the userinfo subcomponent of a URI, which allows remote attackers to discover cleartext credentials because they may appear in SNI data. The vulnerability has been fixed in mitmproxy 7.0.3 and above. ![]() Unless one uses mitmproxy to protect an HTTP/1 service, no action is required. ![]() 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. This means that a malicious client/server could smuggle a request/response through mitmproxy as part of another request/response's HTTP message body. ![]() ![]() In mitmproxy 7.0.2 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. Mitmproxy is an interactive, SSL/TLS-capable intercepting proxy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |