Skip to main content

Hacking Windows 10 UWP App: DLL Injection & common Vulnerabilities

I recently started working on  widows 10 Apps( Apps not Applications) security. Before diving deep in hacking terms lets try to understand what's new in Windows 10 UWP( Universal Platform) as compared to old Apps. Lets begin with how apps actually work on windows 10(desktop/tablet). Now windows 10 comes with a container only for running apps inside the isolated environment. By default, /APPCONTAINER(Linker Flag) is off. This option modifies an executable to indicate whether the app must be run in the appcontainer process-isolation environment. Specify /APPCONTAINER for an app that must run in the appcontainer environment—for example, a Windows Store app. (The option is set automatically in Visual Studio when you create a Windows Store app from a template.) For a desktop app, specify /APPCONTAINER:NO or just omit the option. The /APPCONTAINER option was introduced in Windows 8.
Now there is no registry entry concept for these app in the System HIVE rather they install they own hive control by container(ApplicationFrameHost.exe).  So as soon as you install app it will go inside Somewhere/WindowsApp/AppName. The somewhere is a variable generally you find it inside system Windows directory. Rest of roaming & local data will be saved in the same place as for the other App or applications.
Windows UWP APP Hacking

Windows is also running a project Centennial to convert old apps into UWP format. Lets now examine the level of security these apps really do provide.
Lets go in Owasp top way and analyze.
Insecure Local storage:
Yea as the data is in local directory folder it can be easily accessed. It not like you have root (in android), little privileged escalation will do in case of windows.
Reverse Engineering:
It not as easy as for android apks but with little knowledge of ollydbg you can really do magic on windows app. Local data also not check for integrity so if you want to change any text & internal detail  that are shown in UI & there in local data assets then you can easily tamper it.
DLL Injection:
Yes this will again gonna haunt windows apps. I tried and simple thread hijack is working absolutely fine. With frameworks like easyhook & frida you can change extract & hackers can create modules to easily hack info from the apps.
More secured as compared to android where you have to do proper ssl/tls implementation your self. Even IOS app store is going complete ssl/tls soon.

Rest I will cover in another post on how to hack & identify security flaws into Windows10 UWP app. Any comment or suggestion will be appreciated.


  1. as the /APPCONTAINER is just a linker flag, can you patch it out of a compiled exe?

    1. Let me try it out.. If there are not many dependency with UWPHost.dll then it should work.

  2. This comment has been removed by the author.


Post a Comment

Popular posts from this blog

Animated Cursor Vulnerability

Step1: create two file on attacker side 1) default index.html and 2) cursor file to load Now save the proof of concept in a txt file(cursor.txt). use above command to cut down the hex part from proof of concept and paste it in buffer.ani Step2 :upload the above two files in your apache webserver.  Step3: Try to open index.html from window-xp and analyse the behavior of IE using ollydgb in order to find the offset address where EIP will get over written. Attach IE in ollydgb and put malicious url in it. As we can see now that EIP is overwritten with 42424242 that means this place is our offset. Now we will put the address of jump instruction in place of 42424242 which we will get from user32.dll by searching for command JUMP DWORD [EBX],now we jumped at ebx because it contain the malicious .ani file address. Just go into view=>executable=>user32.dll , press enter. Now try to find a jump [ebx] instruction in user32.dll by pressing ctrl

Assignment 01(Enroll TO Offensive-Security Course)

Steps 1:download the page. 2:open fc4.js in your favourite editor and add following lines in it or just replace it with vode given below. 3:then open the download html file in browser and fill the form with your email and a garbage value string. 4:thats it? it will show you the real security string?? yeah but  ...theirs another challenge waiting for you ... :D function fc4me(srvstr) {    if(! || !document.pleazfc4me.securitystring.value) {       alert("Please fill in all the required fields!");       return false;    }    else {       document.pleazfc4me.submit();     }    var t=hexMD5("\x74\x72\x79\x68\x61\x72\x64\x65\x72"+srvstr) alert(t) document.write(t) } Finally Got In :-)