User Tools

Site Tools


This is an old revision of the document!

A PCRE internal error occured. This might be caused by a faulty plugin

Note that phishing attacks are out of scope ===== Information Flow Channels ===== In this section we are trying to highlight various fields in JavaScript that an attacker can use to transmit information. We distinguish between immediate channels were modifying this fields sends information to an attacker and delayed channels were no information is sent to the attacker until the user performs some action. ==== Delayed Channels ==== * href attribute of links (<a>) * form submission (elements of the form) ==== Immediate Channels ==== * cross-site loading tags (in the DOM) * script (src attribute) * link (href attribute), for stylesheets * img (src attribute) * video (src attribute or source elements) * audio (src attribute or source elements) * object/embed (flash, java applets, etc.) * ifame (src attribute) * XmlHttpRequest (XHR) * form.submit * postMessage ===== Storage ===== For storage channels data is not directly transmitted to an outside source, however any security labels need to be persisted along with the data or these need to be delayed channels. * cookies * * sessionStorage (html5 web storage) * localStorage (html5 web storage) * persistence mechanisms for flash (or other plugins) ===== Security Lattice ===== We assume that each origin may be its own security principal. In addition we have a LOCAL_ONLY label for data that should never leave the client. ===== Confidential Fields ===== * passwords -- allow sending to submission origin but only if not influenced by another principal. Perhaps also restrict output channels to form submission and XHR? * geolocation -- LOCAL_ONLY, unless the user authorizes its release (this would allow us to possibly securely loosen the current restrictions on geolocation). * HTML elements/attributes marked as confidential by the website's developers. ===== XHR ===== Since XHR can be used to pull sensitive data from different pages we need to handle its results with some care. * By default SSL secured resources are treated as confidential to the origin. * By default other results from XHR are treated as public * Both of the above cases may be changed by the developer via HTTP headers ===== DOM ===== In this section we discuss a possible approach to limit a scripts access to the DOM. * an external configuration file specifies which external scripts have access to which DOM elements * local script files and inline JavaScript have no restriction to the DOM * note that this will not stop all forms of XSS attacks but might limit the number of characters available to write the attacking script (e.g. the DB fields with size limits) ===== Mashup Use-Cases ===== * analytics -- do not need access to the DOM? * most advertisements -- need only modify/select specific DOM elements * embedded maps, videos, etc. -- generally only modify specific DIV/SPAN elements * target-word adds -- need extensive access to the DOM (example can be seen at:,2626-4.html) ===== Exfiltration ===== TODO

projects/policy_discussion.1273965520.txt.gz · Last modified: 2010/05/15 23:18 by disnet