GET What else can the .io browser / blog know about you / Sudo Null IT News FREE

Everyone knows that piece inside the browser, you cannot elicit enough information approximately its exploiter using simple JavaScript. Service information, so much as the name of the browser engine, operating system and their versions, although IT gives a unspecialised theme of ​​the user (and the audience as a whole), but is static non super.

For comprehensive user analysis, the User-Gem State is victimized .in Universal Analytics, only with the help of nonpartisan software components track and placed somewhere in the computer's memory next to the web browser, you tooshie also collect user information. Information obtained directly from the web browser's storage will allow analysis of both an individual drug user and the entire audience. Here we will consider a house of browsers on the Webkit engine and on a specific example of the Google Chrome browser.

Browser equally a depositary of interesting information

Each day, millions of people trust their web web browser with the most secret information: personal and banking information, lists of selected sites. About of the really "tasty" information (primarily for attackers) is hidden both by the browser itself (password managers with encryption) and network resources that people employ via the browser (securely written and debugged codification, SMS alerts / confirmations etc). But beyond that, data remains open and easily accessible, such as the germ code of the pages. Indeed, it is in that respect that the absolute majority of that material is located, on the basis of which a comprehensive analysis of users john be ready-made. And this physical is by no means just field in nature.

Browsers themselves (specially those based on Chromium) are built in such a fashio that as little as contingent selective information "leaked" to the outside world about users. That is, the developers are trying in every possible manner to protect mass from all sorts of, even if insignificant leaks. Google Chrome, for example, creates its own sandbox for apiece sort tab in the form of a separate process. You can come up out all but the details by clicking on the local link: chromium-plate: // memory It is logical to assume that for each one so much segregated process pill stores the source code of its have page.

How to obtain out what the browser knows?

The browser process is no different from another processes of the operating system of rules, and therefore it also stores all its information in RAM in the Lapplander way and all the assonant principles of sphere memory are typical for it . Package components, running within the OS, are on the same software level as the browser. This makes it latent to read the web browser retention, remove its garbage dump .

For demonstration, a small test send off in C # was created, which allows collecting source code samples from browser memory. The beginning code of the project rear end be viewed in the BitBucket repository . A utility for straightforward use is here .

Instantly IT's deserving understanding what the quality of collecting information from the source codes of open browser pages located in memory depends on. Chromium is an OpenSource project, so it's enough to dig into its source code a trifle to clarify many basic aspects.

For example, how the page of a web document is arranged. The Document class , which is part of the WebKit engine, has the following code (C ++):

          ... // "personify element" as defined by HTML5 (https://hypertext markup language.specification.whatwg.org/multipage/dom.html#the-body-element-2). // That is, the first dead body or frameset tyke of the document element. HTMLElement* organic structure() const; // "HTML body element" as defined aside CSSOM View spec (http://dev.w3.org/csswg/cssom-view/#the-html-body-element). // That is, the first body child of the text file element. HTMLBodyElement* firstBodyElement() const; ... HTMLHeadElement* head() const; ...                  

From this piece, one can evaluate, for instance, that the browser stores all information about the entities of a web foliate in objects that are hierarchical in structure. You can verify this by looking at the catalogue of all HTML elements known to the WebKit engine.

Combining this information with knowledge more or less how the OS allocates memory for a freshly computer program physical object, it turns out that the HTML computer code for the page can be in totally fragmented human body.

Memory scanning and intelligence isolation

Suppose one and only of the users has opened a new tab in his browser ( this one ). What in that simple type, information technology would appear, can be extracted?

For example, what the exploiter was looking at for in the search engine, and what has not yet been erased by the browser from memory:

                      
              
                Группа подсказок:              
              
                
                                      какой фильм посмотреть                                  
                
...
              
            
                  

You can find prohibited whatsoever physical data. For example, a specific user's mailbox:

                      
              
                                                  nastya.ivanova                              
              
                
                  
...
                  
...
                
              
            
                  

Victimization the dump analyzer, we also managed to get the entire source code of the page. Apparently, someplace in the program code of the browser, a line is cast containing the entire generator code of the webpage. You can analyze it both manually and with the help of various HTML parsers.

Often useful selective information is obtained direct the mechanism of the so-called "cross-site sexual unio." For example, when convinced web resources support authorization through a Google+ account, Facebook, etc. In this case, IT leave already be possible to obtain the analytical information closest to the specific user.

Suppose the target user has a google account and this substance abuser has commented on a specific entity happening the place that is paired with his Google account. In this grammatical case, most of the information around the google exploiter wish be encapsulated inside the germ code of the network page. Here is an example part of a dump that can cost extracted from most pages intermingled with Google:

                      
              
Nastya         Ivanova
              
прокомментировал видео на YouTube              
            
                          Доступно всем в Интернете              -              2014-04-05                        undefinedundefinedundefined            
              
                undefined              
              
                
                  Dear non russian speakers! For good agreement the                         Soviet Anthem you should hear and understand information technology on                         russian language. Interpretation is non sol bad just                         meaning is malformed here and there. And thats because                         English is not so rich language as Russian I think ;)                
              
            
                  

At least we managed to get under one's skin a link to the exploiter profile, his name and surname. Supported this information alone, a banging-scale ingathering of substance abuser information can be deployed.

What is the result?

It ofttimes happens that mountainous web projects release divide applications for their clients. These applications, as a rule, operate with the browser at the same level - at the operating system storey. This approach not alone simplifies some functions for the user, but also collects valuable deductive data virtually it, which it is rarely manageable to collect within the browser itself victimization standard net analytics methods . Close to client application manufacturers may even receive deeply personal information from the web browser's memory in order to "know" their drug user as a great deal A possible.

Privileged the browser memory contains a huge amount of information about the user. Basic pieces can be extracted using a simple march memory analyzer. Moreover, in these pieces English hawthorn curb information of a widely range. Ultimately, it is these basic pieces that can buoy form the basis of a comprehensive analysis of both an separate user and an entire audience.

Abstract

• The source code of the project, which collects data about the user, tail end be found here .
• An analogue of this process is the usage of User-ID in Google Analytics.
• The all but accurate user data terminate atomic number 4 obtained through cross-locate sexual unio (accounts of social networks).

DOWNLOAD HERE

GET What else can the .io browser / blog know about you / Sudo Null IT News FREE

Posted by: hendersonpentrong1942.blogspot.com

Share this post