Top security threats to Flash/Flex applications and how to avoid them

1. Top security threats to Flash/Flex applications and how to avoid them @EladElrom

3. Senior Flash Engineer & Lead

4. Technical Writer

5. FlashAndTheCity Organizer

7. Flash Sandbox “The sandbox defines a limited space in which a Macromedia Flash movie running within the Macromedia Flash Player is allowed to operate. Its primary purpose is to ensure the integrity and security of the client’s machine, and as well as security of any Macromedia Flash movies running in the player."

8. intro Slide from Deneb Meketa's security presentation at MAX

9. Decompiling and modifying swf file

10. Decompile The concept of downloading Flash applications, decompiling, modifying them, and then re-compiling them is one of the oldest & most used cross-scripting techniques out there. Hackers’ use programs such as Sothink SWF decompiler software which allows them to modify the swf.

11. Decompile Flex Apps Not many developers are aware of the fact that these decompilers are now capable of decompiling Flex projects in addition to Flash applications. Let’s take a look at this simple example.

12. After the project is restored, you can then import the project back into Flash builder and change the project. Phishing attack is when a hacker tries to obtain user’s sensitive information by impersonating as a trustworthy entity.

13. Hacking a template site As a second example I went to one of these Flash template site and used a Web Proxy to extract the swf URL and download the swf file to my desktop, then decompiled and opened in Flash Professional

14. Export to FLA

15. View .fla

16. Loading the Flash app SWF file into another project

17. Hackers gain access Slide from Deneb Meketa's security presentation at MAX

18. Change properties on runtime Loading a swf file belonging to a Flex project and then having the accessing application make changes to the access application. In the example below the accessing application gains access to an application, and I was then able to change the text property on a label and even use a login service method. Create a new project.

19. Cross Domain Policy At this point we are loading the accessed application from the same domain; however, if you place the accessed application and the accessing application on two separate domains and place a domain policy that allows accessing the domain from any domain, as in this example below, it will work.

20. Allow cross domainwho can access? https used for Encryption, Authentication user, change data Avoid: allowInsecureDomain("*");

21. Id request w/ Custom request headers - control what can be accessed All - any port Master Only - port 843 none - no socket policy files allowed

22. Allow ports List of TCP and UDP port numbers http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

23. Attacker figure out application source code

24. Phishing for public methods In this example we have access to the source code; however, in case the attacker does not have access to the source code, they can find out the source code in two ways. Once the content is loaded we can actually place a break point and see all the methods we have access to, see figure below.

25. Decompile accessed app Additionally, using decompiling software, the attacker can decompile the accessed application and browse through the classes

26. Accessing other domain through the accessed application

27. Similarly to the application I showed you previously, an attacker could load a SWF from a domain that has access to other domain and than make un-authorized service calls. For instance, let’s say that DomainA allow access to DomainB, as you can see from the Cross Domain policy below: Access SWF from another SWF

28. Security.allowDomain(“*”) Avoid global (wild card) permissions!

29. Load SWF and access The accessing application can load the SWF and access the service class to make an illegal call, and then it can retrieve the data. For instance, let’s assume that a site allows a certain authorized domain to make service calls but the API is not public. If the authorized domain holds a SWF that can be accessed, one can use that SWF to gain access to the API and make un-authorized service calls. this.content.document.service.send();

30. Code sample

31. How to avoid cross-scripting attacks

32. Solution #1 Setting a restricted cross-domain policy that limits the domains that can access the application

33. Solution #2 Use code obfuscation software such as secureSWF from Kindisoft (www.kindisoft.com/), which helps you to protect your ActionScript from Flash decompilers.

34. Solution #3 Avoid using Security.allowDomain(“*”) method to permit access to all swfs. Set the ones you allow access.

35. Cross-site scripting (XSS) vulnerability

36. What is XSS? The idea is to involve more than one site, and that’s where the name (Cross-site) came from, a second site injects a script and can do anything it wants with the page. Examples?

37. Account theft Account theft - Attackers can grab cookie information, which can lead to account hijacking since many cookies holds account information.

38. Change page content Changing content on a page - Misleading user to re-enter their information on a phony site, place incorrect content or read user’s cookies.

39. Vulnerability in Flex applications Flash Player is not vulnerable to cross scripting directly since the byte-code get compiled through the Virtual Machine (VM), However Flash is often used on a page that includes other scripts and your application may interact with other Web pages elements and that can open a security hole since Web page that generate content dynamically without filtering the results first. Attackers can exploit your application and create XSS.

40. Inbound/outbound Slide from Deneb Meketa's security presentation at MAX

41. Cross-Scripting attack to a WebPage from Flex

42. Simple application example

43. Hackers can redirect <script>alert('Test')</script> <script type="text/javascript">window.location = "http://www.google.com/"</script>

44. Malicious data injection

45. What’s Malicious data injection? In cases where a Web Page have permissions to reading and writing from and to a Web Page an attacker can abuse these and rewrite the a web page or redirect users from the Web Page to a phishing site, this type of a attack is know as malicious data injection attack or Script injection.

46. Flash malicious data injection attack The attacker can inject data and create a cross-site scripting (XSS) attack. Coding in ActionScript and using APIs such as ExternalInterface, navigateToURL or getURL. The attacker can than redirect the URL and even post a JavaScript code, which would capture the user’s cookies with personal information.

47. Example Let’s say we need a script to retrieve a parameter that was passed through the URL into the Flex application. As you know you can pass variables using FlashVar and than use the following syntax in Flex 4 To read the parameter: FlexGlobals.topLevelApplication.parameters.name However in case you want to pass the parameters through the URL you need to call the SWF directly like so: MyApp.swf?name=Elad My code allows me to read the parameter from the URL without calling the SWF directly.

48. How it works? Here is how it works. I am registering a callback Javascript function called getParams and once the user click on a button I am calling the Javascript method getURLString, which retrieve the URL parameter and pass it back to the callback.

49. Example application

50. Hacker abuse loophole ?name=Elad I pass the following parameter: ?name=%3Cscript%3Ealert('Elad')%3C/script%3E

51. Cross-site scripting through navigation URLs

52. Attacking browser example Attacking browser navigation URLs is a popular attack. Similar to the example I showed you at "Malicious data injection" section, attackers can inject data through URL. In addition to passing data through FlashVars it's common to use deep linking to change the application state. The application takes params through the URL and than create a link on the application.

54. History Management vulnerability in Flex 3

55. Flex 3 History management The same type of cross-site scripting we just showed you were found in the History Management handled by historyFrame.html in Flex 3. The vulnerability occurs in code used by the History Management feature. In case you use Flex 3 and use the History management features you need to upgrade to at least Flex 3.0.2 SDK Update or just replace the HTML files from Flex 3.02.

56. How to avoid Cross-Scripting attack

57. Whitelisting & Blacklisting The way to avoid must of cross-scripting attacks is to sufficiently sanitize user-supplied data, what it mean is that it’s a good practice to apply the same best practices as old-fashioned web application and to filter the data that user enters to insure that the user entered a proper format and contains only expected data. To avoid this type of vulnerability you can add a code to your Flex/Flash application that will stripe HTML tags, tag attributes, values, Javascript, CSS, HTML and URL. You can take the whitelist or blacklist approach in regards to validating the data. Whitelist is preferred, however whitelisting isn’t always possible so blacklisting can be used.

58. allowScriptAccess

59. allowScriptAccess options Slide from Deneb Meketa's security presentation at MAX

60. Set allowScriptAccess correctly Slide from Deneb Meketa's security presentation at MAX

61. Find HTML tags

62. Use RegExp to avoid attacks I am using the RegExpValidator component and pass the RegExp "((3C)|<). In case there is no match you’ll get: “field is invalid”. You can insert all the RegExp and see if you get zero results, which means that the expression was present. To read more see Symantec article: http://www.symantec.com/connect/articles/detection-sql-injection-and-cross-site-scripting-attacks

63. Update Flash Player and SDK often Updating Flash Player and SDK. Adobe is constantly working to fight attackers. For instance during the upgrade to Flex SDK 3.4 Adobe have solved an issues regarding ticket CVE-2009-1879, which took care of Cross-site scripting (XSS) vulnerability in the index.template.html in SDK 3.3. When the installed Flash version was older than a specified requiredMajorVersion value it allowed the remote attackers to inject arbitrary web script or HTML via the query string.

64. Common security on local builts:Flash Access The Internet

65. swf trying to access the internet SecurityError: Error #2028: Local-with-filesystem SWF file file:///file.swf cannot access Internet URL http://...

66. Solution http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager04.html Add "trusted" locations 6 - Click on Edit Locations 7 - Click on Add Location 8 - Click on Browse for folder 9 - Select the folder were your flash app is

67. Links: Elad Elrom’s articles http://www.insideria.com/2009/12/top-security-threats-to-flashf.html http://insideria.com/2010/06/top-security-threats-to-flashf-1.html The Flash Player Security Topic Center: http://www.adobe.com/devnet/security OWASPhttp://www.owasp.org/index.php/Category:OWASP_Flash_Security_Project Q&A