CAPEC-182 Detail

An attacker tricks a victim to execute malicious flash content that executes commands or makes flash calls specified by the attacker. One example of this attack is cross-site flashing, an attacker controlled parameter to a reference call loads from content specified by the attacker.

Execution Flow

1) Explore

[Find Injection Entry Points] The attacker first takes an inventory of the entry points of the application.

Technique

• Spider the website for all available URLs that reference a Flash application.
• List all uninitialized global variables (such as _root.*, _global.*, _level0.*) in ActionScript, registered global variables in included files, load variables to external movies.

2) Experiment

[Determine the application's susceptibility to Flash injection] Determine the application's susceptibility to Flash injection. For each URL identified in the explore phase, the attacker attempts to use various techniques such as direct load asfunction, controlled evil page/host, Flash HTML injection, and DOM injection to determine whether the application is susceptible to Flash injection.

Technique

• Test the page using direct load asfunction, getURL,javascript:gotRoot("")///d.jpg
• Test the page using controlled evil page/host, http://example.com/evil.swf
• Test the page using Flash HTML injection, "'>
• Test the page using DOM injection, (gotRoot(''))

3) Exploit

[Inject malicious content into target] Inject malicious content into target utilizing vulnerable injection vectors identified in the Experiment phase

Prerequisites

The target must be capable of running Flash applications. In some cases, the victim must follow an attacker-supplied link.

Skills Required

The attacker needs to have knowledge of Flash, especially how to insert content the executes commands.

Resources Required

None: No specialized resources are required to execute this type of attack. The attacker may need to be able to serve the injected Flash content.

Mitigations

Implementation: remove sensitive information such as user name and password in the SWF file.
Implementation: use validation on both client and server side.
Implementation: remove debug information.
Implementation: use SSL when loading external data
Implementation: use crossdomain.xml file to allow the application domain to load stuff or the SWF file called by other domain.

Related Weaknesses

References

REF-46

Finding Vulnerabilities in Flash Applications
Stefano Di Paola.

REF-47

A Lazy Pen Tester's Guide to Testing Flash Applications
Rudra K. Sinha Roy.
http://www.ivizsecurity.com/blog/web-application-security/testing-flash-applications-pen-tester-guide/

REF-48

Creating More Secure SWF Web Application
Peleus Uhley.
http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html

Submission

Modifications