Détail du CAPEC-86

An adversary exploits web applications that generate web content, such as links in a HTML page, based on unvalidated or improperly validated data submitted by other actors. XSS in HTTP Headers attacks target the HTTP headers which are hidden from most users and may not be validated by web applications.

Flux d'exécution

[Survey the application for public links] Using a browser or an automated tool, an adversary follows all public links on a web site. They record all the entry points (input) that becomes part of generated HTTP header (not only GET/POST/COOKIE, but also Content-Type, etc.)

• Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make special note of any links that include parameters used in the HTTP headers.
• Look for HTML meta tags that could be injectable
• Use a proxy tool to record all links visited during a manual traversal of the web application.
• Use a browser to manually explore the website and analyze how it is constructed. Many browsers' plugins are available to facilitate the analysis or automate the discovery.

[Probe identified potential entry points for XSS vulnerability]

The adversary uses the entry points gathered in the "Explore" phase as a target list and injects various common script payloads to determine if an entry point actually represents a vulnerability and to characterize the extent to which the vulnerability can be exploited. They record all the responses from the server that include unmodified versions of their script.

The adversary tries also to inject extra-parameter to the HTTP request to see if they are reflected back in the web page or in the HTTP response.

• Manually inject various script payloads into each identified entry point using a list of common script injection probes and observe system behavior to determine if script was executed.
• Use an automated injection attack tool to inject various script payloads into each identified entry point using a list of common script injection probes and observe system behavior to determine if script was executed.
• Use a proxy tool to record results of manual input of XSS probes in known URLs.

[Craft malicious XSS URL] Once the adversary has determined which parameters are vulnerable to XSS, they will craft a malicious URL containing the XSS exploit. The adversary can have many goals, from stealing session IDs, cookies, credentials, and page content from the victim.

• Change a URL parameter which is used in an HTTP header to include a malicious script tag. Because it is in the header it may bypass validation.
• Send information gathered from the malicious script to a remote endpoint.

[Get victim to click URL] In order for the attack to be successful, the victim needs to access the malicious URL.

• Send a phishing email to the victim containing the malicious URL. This can be hidden in a hyperlink as to not show the full URL, which might draw suspicion.
• Put the malicious URL on a public forum, where many victims might accidentally click the link.

Conditions préalables

Target software must be a client that allows scripting communication from remote hosts.

Compétences requises

To achieve a redirection and use of less trusted source, an adversary can simply edit HTTP Headers that are sent to client machine.
Exploiting a client side vulnerability to inject malicious scripts into the browser's executable process.

Ressources nécessaires

The adversary must have the ability to deploy a custom hostile service for access by targeted clients and the abbility to communicate synchronously or asynchronously with client machine. The adversary must also control a remote site of some sort to redirect client and data to.

Atténuations

Design: Use browser technologies that do not allow client side scripting.
Design: Utilize strict type, character, and encoding enforcement
Design: Server side developers should not proxy content via XHR or other means, if a http proxy for remote content is setup on the server side, the client's browser has no way of discerning where the data is originating from.
Implementation: Ensure all content that is delivered to client is sanitized against an acceptable content specification.
Implementation: Perform input validation for all remote content.
Implementation: Perform output validation for all remote content.
Implementation: Disable scripting languages such as JavaScript in browser
Implementation: Session tokens for specific host
Implementation: Patching software. There are many attack vectors for XSS on the client side and the server side. Many vulnerabilities are fixed in service packs for browser, web servers, and plug in technologies, staying current on patch release that deal with XSS countermeasures mitigates this.

Faiblesses connexes

Références

REF-1

Exploiting Software: How to Break Code
G. Hoglund, G. McGraw.

REF-69

OWASP Cheatsheets
https://www.owasp.org/www-community/xss-filter-evasion-cheatsheet

REF-476

XSS vulnerabilities in Google.com
Watchfire Research.
http://seclists.org/fulldisclosure/2005/Dec/1107

Soumission

Modifications