Client Network Footprinting (using AJAX/XSS) |
Attack Pattern ID: 85 (Detailed Attack Pattern Completeness: Complete) | Typical Severity: Very High | Status: Draft |
Summary
This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. In many XSS attacks the attacker must get a "hole in one" and successfully exploit the vulnerability on the victim side the first time, once the client is redirected the attacker has many chances to engage in follow on probes, but their is only one first chance. In a widely used web application this is not a major problem because 1 in a 1,000 is good enough in a widely used application.
A common first step for an attacker is to footprint the environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well known ports, network locations and so on.
Description
Footprinting can be executed over almost any protocol including HTTP, TCP, UDP, and ICMP, with the general goal of gaining further information about a host environment to launch further attacks. By appending a malicious script to an otherwise normal looking URL, the attacker can probe the sysem for banners, vulnerabilities, filenames, available services, and in short anything the host process has access to. The results of the probe are either used to execute additional javascript (for example, if the attacker's footprint script identifies a vulnerability in a firewall permission, then the client side script executes a javascript to change client firewall settings, or an attacker may simply echo the results of the scan back out to a remote host for targeting future attacks).
Skill or Knowledge Level: Medium
To land and launch a script on victim's machine with appropriate footprinting logic for enumerating services and vulnerabilities in Javascript
Design: Use browser technologies that do not allow client side scripting.
Design: Utilize strict type, character, and encoding enforcement
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: 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.
Payload delivered through standard communication protocols, such as Ajax application.
CWE-ID | Weakness Name | Weakness Relationship Type |
---|---|---|
79 | Failure to Preserve Web Page Structure ('Cross-site Scripting') | Targeted |
113 | Failure to Sanitize CRLF Sequences in HTTP Headers ('HTTP Response Splitting') | Targeted |
348 | Use of Less Trusted Source | Targeted |
96 | Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') | Targeted |
20 | Improper Input Validation | Targeted |
116 | Improper Encoding or Escaping of Output | Targeted |
184 | Incomplete Blacklist | Secondary |
86 | Improper Neutralization of Invalid Characters in Identifiers in Web Pages | Secondary |
712 | OWASP Top Ten 2007 Category A1 - Cross Site Scripting (XSS) | Targeted |
692 | Incomplete Blacklist to Cross-Site Scripting | Targeted |
Nature | Type | ID | Name | Description | View(s) this relationship pertains to |
---|---|---|---|---|---|
ChildOf | Attack Pattern | 169 | Footprinting | Mechanism of Attack (primary)1000 |
Shreeraj Shah, "Ajax footprinting for Web 2.0 applications", http://www.net-security.org/dl/articles/Ajax_fingerprinting.pdf