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.

  3. Thanks for sharing an all around clarified article. This blog definitely helps every individual who need to fix DLL in Window 10. I additionally confronted a DLL mistake in my Windows 10 then I discovered a blog distributed on the DLLWin site on How to Fix Missing DLL Files in Windows 10/8/7?? Genuinely I am amazed after reading that blog that blog they clarified it well overall and provide in depth detail on to how to Fix Missing DLL Files in Windows 10/8/7.


Post a Comment

Popular posts from this blog

Installing vmware-11.0 on Ubuntu 15.04 Using kernel Patch

curl -o /tmp/vmnet-3.19.patch cd /usr/lib/vmware/modules/source tar -xf vmnet.tar patch -p0 -i /tmp/vmnet-3.19.patch tar -cf vmnet.tar vmnet-only rm -r *-only vmware-modconfig --console --install-all References:

SSI Injection Attack

SSIs are directives present on Web applications used to feed an HTML page with dynamic contents. They are similar to CGIs, except that SSIs are used to execute some actions before the current page is loaded or while the page is being visualized. In order to do so, the web server analyzes SSI before supplying the page to the user. The Server-Side Includes attack allows the exploitation of a web application by injecting scripts in HTML pages or executing arbitrary codes remotely. It can be exploited through manipulation of SSI in use in the application or force its use through user input fields. It is possible to check if the application is properly validating input fields data by inserting characters that are used in SSI directives, like:  Code: < ! # = / . " - > and [a-zA-Z0-9] Another way to discover if the application is vulnerable is to verify the presence of pages with extension .stm, .shtm and .shtml. However, the lack of these type of pages does not mean that th