Dll hijacking


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Dll hijacking

  1. 1. Dll hijacking<br /> Praveen Kumar [D4rk357]<br /> Information Security Rookie<br />
  2. 2. Introduction<br />DLL Hijacking is very Topic in exploit research and development these days .<br />On 25th of August this year Exploit-DB was flooded with so many DLL Hijacking exploits that they stopped accepting it in the database and they mentioned these exploits in their blog post.<br />Nearly all window application including this powerpoint (w00t w00t) I am using is vulnerable to it.<br />
  3. 3. Introduction <br />
  4. 4. Is DLL Hijacking New vector?<br />While Searching for DLL Hijacking on Internet I saw mention of this exploit from as long as back in 2000(maybe you can find its mention much before that).<br />What opened the floodgates of DLL hijacking exploits was a exploitation method by The Leader(maybe he also borrowed it from somewhere else) which could be used as if for nearly all applications to pawn them.<br />
  5. 5. Example of Code<br />
  6. 6. What is DLL Hijacking<br />In simple words, DLL Hijacking is the vulnerability which can be used to make any vulnerable application to load malicious DLL by exploiting its DLL search order mechanism there by taking complete control over the system. Attacker can trick the user to open the documents/video/movies from the remote share where user can place malicious version of legitimate DLL. So when user launches the application to view such remote content, application will load these malicious DLLs instead of original DLL.<br />
  7. 7. Microsoft Windows DLL Search Path Weakness<br />When a program executes under Microsoft Windows, it may require additional code stored in DLL library files. These files are dynamically located at run time, and loaded if necessary. A weakness exists in the algorithm used to locate these files.The search algorithm used to locate DLL files specifies that the current working directory is checked before the System folders. If a trojaned DLL can be inserted into the system in an arbitrary location, and a predictable executable called with the same current working directory, the trojaned DLL may be loaded and executed. This may occur when a data file is accessed through the 'Run' function, or double clicked in Windows Explorer.<br />
  8. 8. Offensive-Security Video<br />
  9. 9. Solutions ??<br />Sorry but there is no fix to this yet  .<br />Microsoft has released an Security Advisory citing this problem and mentioning about these mitigations<br />Disable loading of libraries from WebDAV and remote network shares<br />Disable the WebClient service<br />Block TCP ports 139 and 445 at the firewall<br />Microsoft has also introduced new registry key CWDIllegalInDllSearch to safeguard individual or All applications from this vulnerability. Below is the link to KB article.<br />
  10. 10. Questions ??<br />Maybe I will not be able to answer all but we have a lot of ppl in audience who can . So start shooting <br />
  11. 11. Thanksgiving<br />Thanks to Rockey killer , FB1H2S, b0nd, punter,prashant,vinay,and all h4ck3r.in and garage4hackers.com<br />Speacial Thanks to everyone in the audience for not sleeping :D .<br />