All Projects → koto → Mosquito

koto / Mosquito

XSS exploitation tool - access victims through HTTP proxy

Programming Languages

tcl
693 projects

Mosquito

by Krzysztof Kotowicz - [email protected]

Mosquito is a XSS exploitation tool allowing an attacker to set up a HTTP proxy and leverage XSS to issue arbitrary HTTP requests through victim browser (and victim cookies).

Mosquito is extremely valuable when exploiting Google Chrome extensions, because via using XSS is extension content script it can usually issue arbitrary cross-domain HTTP requests (breaking the usual Same Origin Policy restrictions).

With this tool attacker can exploit content-script XSS vulnerabilities in extensions based on manifest v1 and v2.

Introduction

Mosquito is a tool to exploit common XSS vulnerabilities in Google Chrome extensions. Chrome extensions can often submit unrestricted XHR requests to any domain, making them a perfect tool to abuse. It allows the attacker to easily generate XSS payloads that setup peristent connection from victim browsers to given Mosquito server. Mosquito server in turn allows the attacker to instrument victim's XMLHttpRequest object via setting up a HTTP Proxy.

Upon successful exploitation attacker can access websites through victim's browser and easily hijack user sessions (sort of like XSS-Proxy). If exploited Google Chrome extension had wildcard URL patterns (and lots of them do), attacker can also navigate to sites outside exploited origin (e.g. Gmail domain, intranet addresses etc.). Think of it as XSS in Chrome Extesion to HTTP Proxy bridge

While written originally to target XSS vulnerabilities in Chrome Extensions, this tool can also be used to exploit "standard" XSS flaws in websites, in this situation however being severely limited by Same Origin Policy restrictions, allowing the attacker to make arbitrary request to the origin where XSS was exploited only.

Mosquito was originally based on MalaRIA, a proof-of-concept made by Erlend Oftedal demonstrating a proxy abusing unrestricted cross domain policies and it is heavily influenced by its architecture. However lots of changes have been introduced, and the project is now fully Python-based, multi-threaded, HTTPS compatible thanks to mitmproxy, and WebSockets protocol is used for transport.

Requirements

Installation

  1. Clone the repository

    $ git clone https://github.com/koto/mosquito.git $ cd mosquito $ git submodule update --init --recursive

  2. Install dependencies

    $ easy_install pyopenssl $ easy_install pyasn1 $ easy_install flask

Usage

  1. Find XSS vulnerability in Google Chrome extension

    Scan, review the code etc. See e.g. I'm in your browser, pwning your stuff presentation or my blog

  2. Do the dance!

  3. Launch Mosquito server

    $ python mosquito/start.py 8082 4444 --http 8000

    This will launch Mosquito server with HTTP proxy on 127.0.0.1:4444 and Mosquito WebSocket proxy on *:8082. Additionally webroot/ dir will be served over *:8000

  4. Generate mosquito hook at http://localhost:8000/generate.html. Victim MUST be able to connect to base_url HTTP server and to ws_host:ws_port WebSocket server.

  5. Inject hook into extension installed in victim's browser. Multiple victims can connect simultaneously to the same Mosquito server.

  6. Use localhost:4444 as your HTTP proxy. You now can use Burp or your browser to send requests and receive responses. Use 'http://mosquito' address in a proxy to get info about currently connected victims and switch contexts.

License

Mosquito - Chrome Extension exploitation tool Copyright (C) 2013 Krzysztof Kotowicz - http://blog.kotowicz.net

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

See also

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].