Dark Mode
Capec-32 Detail
XSS Through HTTP Query Strings
Detailed Software Software Software Likelihood: High Typical Severity: High
Parents: 588 591 592
Tools: 18
An adversary embeds malicious script code in the parameters of an HTTP query string and convinces a victim to submit the HTTP request that contains the query string to a vulnerable web application. The web application then procedes to use the values parameters without properly validation them first and generates the HTML code that will be executed by the victim's browser.
Not present
| External ID | Source | Link | Description |
|---|---|---|---|
| CAPEC-32 | capec | https://capec.mitre.org/data/definitions/32.html | |
| CWE-80 | cwe | http://cwe.mitre.org/data/definitions/80.html | |
| REF-1 | reference_from_CAPEC | G. Hoglund, G. McGraw, Exploiting Software: How to Break Code, 2004--02, Addison-Wesley |
Explore
-
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 links they find.
| Techniques |
|---|
| Use a spidering tool to follow and record all links. Make special note of any links that include parameters in the URL. |
| Use a proxy tool to record all links visited during a manual traversal of the web application. Make special note of any links that include parameters in the URL. Manual traversal of this type is frequently necessary to identify forms that are GET method forms rather than POST forms. |
| Use a browser to manually explore the website and analyze how it is constructed. Many browser's plugins are available to facilitate the analysis or automate the URL discovery. |
Experiment
-
Probe public links for XSS vulnerability: The adversary uses the public links gathered in the "Explore" phase as a target list and requests variations on the URLs they spidered before. They send parameters that include variations of payloads. They record all the responses from the server that include unmodified versions of their script.
-
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.
| Techniques |
|---|
| Use a list of XSS probe strings to inject in parameters of known URLs. If possible, the probe strings contain a unique identifier. |
| Use a proxy tool to record results of manual input of XSS probes in known URLs. |
| Techniques |
|---|
| Change a URL parameter to include a malicious script tag. |
| Send information gathered from the malicious script to a remote endpoint. |
Exploit
-
Get victim to click URL: In order for the attack to be successful, the victim needs to access the malicious URL.
| Techniques |
|---|
| 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. |
- Target client software must allow scripting such as JavaScript. Server software must allow display of remote generated HTML without sufficient input or output validation.
- Ability to send HTTP post to scripting host and collect output
| Low | High |
|---|---|
| To place malicious payload on server via HTTP | |
| Exploiting any information gathered by HTTP Query on script host |
| Integrity | Availability | Confidentiality |
|---|---|---|
| Execute Unauthorized Commands (Run Arbitrary Code) | Execute Unauthorized Commands (Run Arbitrary Code) | Read Data |
| Execute Unauthorized Commands (Run Arbitrary Code) |
- http://user:host@example.com:8080/oradb
- Web applications that accept name value pairs in a HTTP Query string are inherently at risk to any value (or name for that matter) that an adversary would like to enter in the query string. This can be done manually via web browser or trivially scripted to post the query string to multiple sites. In the latter case, in the instance of many sites using similar infrastructure with predictable http queries being accepted and operated on (such as blogging software, Google applications, and so on), a single malicious payload can be scripted to target a wide variety of sites. Web 2.0 type sites like Technorati and del.icio.us rely on user generated content like tags to build http links that are displayed to other users. del.icio.us allows users to identify sites, tag them with metadata and provide URL, descriptions and more data. This data is then echoed back to any other web browser that is interested in the link. If the data is not validated by the del.icio.us site properly then an arbitrary code can be added into the standard http string sent to del.icio.us by the adversary, for example formatted as normal content with a URL and description and tagged as Java, and available to be clicked on (and executed by) any user browsing for Java content that clicks on this trojaned content.