{"id":33050,"date":"2017-08-18T11:47:20","date_gmt":"2017-08-18T15:47:20","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/wikileaks-vault-7-projects.php"},"modified":"2017-08-18T11:47:20","modified_gmt":"2017-08-18T15:47:20","slug":"wikileaks-vault-7-projects","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/wikileaks\/wikileaks-vault-7-projects.php","title":{"rendered":"WikiLeaks &#8211; Vault 7: Projects"},"content":{"rendered":"<p><p>    Today, June 15th 2017, WikiLeaks publishes documents from the    CherryBlossom project of the CIA that was developed    and implemented with the help of the US nonprofit Stanford Research    Institute (SRI International).  <\/p>\n<p>    CherryBlossom provides a means of monitoring the    Internet activity of and performing software exploits on    Targets of interest. In particular,    CherryBlossom is focused on compromising wireless    networking devices, such as wireless routers and access points    (APs), to achieve these goals. Such Wi-Fi devices are commonly    used as part of the Internet infrastructure in private homes,    public spaces (bars, hotels or airports), small and medium    sized companies as well as enterprise offices. Therefore these    devices are the ideal spot for \"Man-In-The-Middle\" attacks, as    they can easily monitor, control and manipulate the Internet    traffic of connected users. By altering the data stream between    the user and Internet services, the infected device can inject    malicious content into the stream to exploit vulnerabilities in    applications or the operating system on the computer of the    targeted user.  <\/p>\n<p>    The wireless device itself is compromized by implanting a    customized CherryBlossom firmware on it; some devices    allow upgrading their firmware over a wireless link, so no    physical access to the device is necessary for a successful    infection. Once the new firmware on the device is flashed, the    router or access point will become a so-called    FlyTrap. A FlyTrap will beacon over the    Internet to a Command & Control server referred to as the    CherryTree. The beaconed information contains device    status and security information that the CherryTree    logs to a database. In response to this information, the    CherryTree sends a Mission with    operator-defined tasking. An operator can use    CherryWeb, a browser-based user interface to view    Flytrap status and security info, plan    Mission tasking, view Mission-related data,    and perform system administration tasks.  <\/p>\n<p>    Missions may include tasking on Targets to    monitor, actions\/exploits to perform on a Target, and    instructions on when and how to send the next beacon. Tasks for    a Flytrap include (among others) the scan for    email addresses, chat usernames, MAC    addresses and VoIP numbers in passing network    traffic to trigger additional actions, the copying of the full    network traffic of a Target, the redirection of a    Targets browser (e.g., to Windex for browser    exploitation) or the proxying of a Targets network    connections. FlyTrap can also setup VPN tunnels to a    CherryBlossom-owned VPN server to give an operator    access to clients on the Flytraps WLAN\/LAN for    further exploitation. When the Flytrap detects a    Target, it will send an Alert to the    CherryTree and commence any actions\/exploits against    the Target. The CherryTree logs    Alerts to a database, and, potentially distributes    Alert information to interested parties (via    Catapult).  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>The rest is here:<br \/>\n<a target=\"_blank\" href=\"https:\/\/wikileaks.org\/vault7\/\" title=\"WikiLeaks - Vault 7: Projects\">WikiLeaks - Vault 7: Projects<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Today, June 15th 2017, WikiLeaks publishes documents from the CherryBlossom project of the CIA that was developed and implemented with the help of the US nonprofit Stanford Research Institute (SRI International). CherryBlossom provides a means of monitoring the Internet activity of and performing software exploits on Targets of interest. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[50],"tags":[],"class_list":["post-33050","post","type-post","status-publish","format-standard","hentry","category-wikileaks"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/33050"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=33050"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/33050\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=33050"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=33050"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=33050"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}