&gt; ...seriously--what can the hijacker do?<p>Introduce arbitrary code and data for your User Agent to execute and decode.<p>This can be something as simple as data alteration to mislead the target or disrupt his communications. However, if the attacker has some Sweet 0-Day Sploit, (or some old-and-busted &#x27;sploit that works on the target&#x27;s old-and-busted User Agent) they can MitM any HTTP session and use that sploit to do $SOMETHING_NEFARIOUS.<p>This isn&#x27;t theoretical. The NSA slides spoke of active attacks against older versions of Firefox shipped in the Tor Browser Bundle. Similar attacks making use of WebRTC to leak data were proposed and fixed, posthaste.<p>An additional benefit of HTTPS is the reduction of metadata provided to passive attackers. (HTTPS sessions encrypt the names of the resources requested from the remote server. There are still ways to get an idea of what&#x27;s being requested, but all an adversary knows for <i>sure</i> is that you&#x27;re talking HTTPS to a particular web server.)