[+] Credits: hyp3rlinx

[+] Website: hyp3rlinx.altervista.org

[+] Source:
http://hyp3rlinx.altervista.org/advisories/MICROSOFT-PPT-VIEWER-CODE-EXEC.txt



Vendor:
===================
www.microsoft.com



Product:
============================
Microsoft PowerPoint Viewer
version: 12.0.6600.1000



Vulnerability Type:
====================================
DLL Hijack Arbitrary Code Execution



Vulnerability Details:
=====================

Microsoft PowerPoint Viewer 'POWERPNT.EXE' will execute arbitrary code if
an attacker can place a DLL named "api-ms-win-appmodel-runtime-l1-1-0.dll"
in users
downloads directory. This exploit does NOT rely on any embedded OLE objects
or CLSID registered COM objects in the document to execute.


1) create malicious DLL named "api-ms-win-appmodel-runtime-l1-1-0.dll"

2) place DLL in users downloads directory via download driveby etc...

3) open an existing .PPT document from the downloads directory e.g.
"C:\Users\Downloads\somefile.ppt"


then BOOOOOM ...


Tested on: Windows 7 SP1 x64



Disclosure Timeline:
=================================================================
Vendor Notification:  February 23, 2016
vendor replies DLL side loading issue already publicly known.

a google search returned following results:

1) examples using embedded OLE objects and MS Word etc
2) old posts
3) examples not referencing "api-ms-win-appmodel-runtime-l1-1-0.dll" DLL

February 29, 2016  : Public Disclosure.



Severity Level:
================
High



Description:
============================================================

vulnerable DLL: "api-ms-win-appmodel-runtime-l1-1-0.dll"
Vulnerable Product:  Microsoft PowerPoint Viewer 'POWERPNT.EXE'

============================================================

[+] Disclaimer
Permission is hereby granted for the redistribution of this advisory,
provided that it is not altered except by reformatting it, and that due
credit is given. Permission is explicitly given for insertion in
vulnerability databases and similar, provided that due credit is given to
the author.
The author is not responsible for any misuse of the information contained
herein and prohibits any malicious use of all security related information
or exploits by the author or elsewhere.

by hyp3rlinx