In public apache mod_isapi exploits, they ask for dlls, and I am unsure what I should put in dll.
I am having a hard time understanding exploits.. How does all of dlls connect to manipulating isapi.dll?
In public apache mod_isapi exploits, they ask for dlls, and I am unsure what I should put in dll. I am having a hard time understanding exploits.. How does all of dlls connect to manipulating isapi.dll? |
|||||||||
|
By default, metasploit requests The idea is that the DLL is forced to be unloaded by the server then requested again by the attacker, resulting in a potential violation of the memory pointer because mod_isapi doesn't properly cleanup the pointers to an unloaded DLL. |
|||
|