CAPECattack pattern

CAPEC-500 WebView Injection

Official page ↗
Abstraction
Detailed
Status
Draft
CAPEC version
3.9

Description

An adversary, through a previously installed malicious application, injects code into the context of a web page displayed by a WebView component. Through the injected code, an adversary is able to manipulate the DOM tree and cookies of the page, expose sensitive information, and can launch attacks against the web application from within the web page.

Execution flow

1. [Explore] [Determine target web application] An adversary first needs to determine what web application they wish to target. 2. [Experiment] [Create malicious application] An adversary creates an application, often mobile, that incorporates a WebView component to display the targeted web application. This malicious application needs to downloaded by a user, so adversaries will make this application useful in some way. 3. [Experiment] [Get the victim to download and run the application] An adversary needs to get the victim to willingly download and run the application. 4. [Exploit] [Inject malicious code] Once the victim runs the malicious application and views the targeted web page in the WebView component, the malicious application will inject malicious JavaScript code into the web application. This is done by using WebView's loadURL() API, which can inject arbitrary JavaScript code into pages loaded by the WebView component with the same privileges. This is often done by adding a script tag to the document body with a src destination to a remote location that serves malicious JavaScript code.

Prerequisites

• An adversary must be able install a purpose built malicious application onto the device and convince the user to execute it. The malicious application is designed to target a specific web application and is used to load the target web pages via the WebView component. For example, an adversary may develop an application that interacts with Facebook via WebView and adds a new feature that a user desires. The user would install this 3rd party app instead of the Facebook app.

Mitigations

• The only known mitigation to this type of attack is to keep the malicious application off the system. There is nothing that can be done to the target application to protect itself from a malicious application that has been installed and executed.

Related

Child of · CAPEC (1)

  • CAPEC-253 Remote Code Inclusion attack pattern

Weakness · CWE (2)

  • CWE-749 Exposed Dangerous Method or Function weakness
  • CWE-940 Improper Verification of Source of a Communication Channel weakness

Referenced by CWE · attack pattern (2)

  • CWE-749 Exposed Dangerous Method or Function weakness
  • CWE-940 Improper Verification of Source of a Communication Channel weakness