COMMON ATTACK PATTERN ENUMERATION AND CLASSIFICATIONLive MITRE record

CAPEC-198

XSS Targeting Error Pages

An adversary distributes a link (or possibly some other query structure) with a request to a third party web server that is malformed and also contains a block of exploit code in order to have the exploit become live code in the resulting error page.

Abstraction

Detailed

Typical severity

Medium

Likelihood of attack

Medium

Understand the attack

What is this attack pattern?

An adversary distributes a link (or possibly some other query structure) with a request to a third party web server that is malformed and also contains a block of exploit code in order to have the exploit become live code in the resulting error page.

Extended description

When the third party web server receives the crafted request and notes the error it then creates an error message that echoes the malformed message, including the exploit. Doing this converts the exploit portion of the message into to valid language elements that are executed by the viewing browser. When a victim executes the query provided by the adversary the infected error message is returned including the exploit code which then runs in the victim's browser. XSS can result in execution of code as well as data leakage (e.g. session cookies can be sent to the attacker). This type of attack is especially dangerous since the exploit appears to come from the third party web server, who the victim may trust and hence be more vulnerable to deception.

Execution flow

How does the attack proceed, step by step?

1

Explore

Survey the application for user-controllable inputs as URL parameters

Using a browser or an automated tool, an adversary follows all public links and actions on a web site. They record all the links, the forms, the resources accessed and all other potential entry-points for the web application, looking for URLs which use parameters.

Techniques used

  • Use a spidering tool to follow and record all links and analyze the web pages to find entry points. Make 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.
  • 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.
2

Experiment

Cause application to return error page

The adversary uses the URLs gathered in the "Explore" phase as a target list and injects various common script payloads and special characters into the parameters to see if an error page occurs, and if the injected payload is executed by the error page.

Techniques used

  • Use a list of XSS probe strings to inject script 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.
  • Use a list of HTML special characters to inject into parameters of known URLs and check if they caused errors

Craft malicious XSS URL

Once the adversary has determined which parameters are vulnerable to XSS through an error page, 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 used

  • Change a URL parameter to include a malicious script tag.
  • Send information gathered from the malicious script to a remote endpoint.
3

Exploit

Get victim to click URL

In order for the attack to be successful, the victim needs to access the malicious URL.

Techniques used

  • 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.

Requirements

What does the attack require?

Prerequisites

  • A third party web server which fails to adequately sanitize messages sent in error pages.
  • The victim must be made to execute a query crafted by the adversary which results in the infected error report.

Skills required

Not stated in the MITRE record.

Resources required

  • None: No specialized resources are required to execute this type of attack.

Defence

How is it prevented and mitigated?

1
Design: Use libraries and templates that minimize unfiltered input.
2
Implementation: Normalize, filter and use an allowlist for any input that will be used in error messages.
3
Implementation: The victim should configure the browser to minimize active content from untrusted sources.
CAPEC-198: XSS Targeting Error Pages — DayBreach Saldırı Sözlüğü · DayBreach