CAPECattack pattern

CAPEC-85 AJAX Footprinting

Low Official page ↗
Abstraction
Detailed
Status
Draft
Likelihood of attack
High
Typical severity
Low
CAPEC version
3.9

Description

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. A common first step for an attacker is to footprint the target 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. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.

Execution flow

1. [Explore] [Send request to target webpage and analyze HTML] Using a browser or an automated tool, an adversary sends requests to a webpage and records the received HTML response. Adversaries then analyze the HTML to identify any known underlying JavaScript architectures. This can aid in mappiong publicly known vulnerabilities to the webpage and can also helpo the adversary guess application architecture and the inner workings of a system.

Prerequisites

• The user must allow JavaScript to execute in their browser

Skills required

• [Medium] To land and launch a script on victim's machine with appropriate footprinting logic for enumerating services and vulnerabilities in JavaScript

Consequences

• Confidentiality: Read Data

Mitigations

• Design: Use browser technologies that do not allow client side scripting. • Implementation: Perform input validation for all remote content.

Related

Can precede · CAPEC (1)

  • CAPEC-63 Cross-Site Scripting (XSS) attack pattern

Child of · CAPEC (1)

  • CAPEC-580 System Footprinting attack pattern

Weakness · CWE (9)

  • CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers weakness
  • CWE-116 Improper Encoding or Escaping of Output weakness
  • CWE-184 Incomplete List of Disallowed Inputs weakness
  • CWE-20 Improper Input Validation weakness
  • CWE-348 Use of Less Trusted Source weakness
  • CWE-692 Incomplete Denylist to Cross-Site Scripting weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation weakness
  • CWE-86 Improper Neutralization of Invalid Characters in Identifiers in Web Pages weakness
  • CWE-96 Improper Neutralization of Directives in Statically Saved Code weakness

Referenced by CWE · attack pattern (9)

  • CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers weakness
  • CWE-116 Improper Encoding or Escaping of Output weakness
  • CWE-184 Incomplete List of Disallowed Inputs weakness
  • CWE-20 Improper Input Validation weakness
  • CWE-348 Use of Less Trusted Source weakness
  • CWE-692 Incomplete Denylist to Cross-Site Scripting weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation weakness
  • CWE-86 Improper Neutralization of Invalid Characters in Identifiers in Web Pages weakness
  • CWE-96 Improper Neutralization of Directives in Statically Saved Code weakness