Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Dave Aitel (dave_at_immunitysec.com)
Date: Sat Feb 01 2003 - 00:57:06 CST
So after writing the RPC locator exploit, I noticed that the service
is not actually vulnerable until it has been initialized
properly. Does anyone have any more information on how often and when
this service is intialized (as opposed to simply started)?
Here is tethereal output illustrating an uninitialized locator service:
192.168.1.101 -> 192.168.1.100 DCERPC Bind: call_id: 5 UUID:
e33c0cc4-0482-101a-bc0c-02608c6ba218 ver 1.0
192.168.1.100 -> 192.168.1.101 DCERPC Bind_ack: call_id: 5 Provider
rejection, reason: Abstract syntax not supported
In my testing environment this is the state of the locator service until
a local user binds to it to begin a lookup.
Other than this, the RPC Locator Service exploit is available as a
CANVAS module. (http://www.immunitysec.com/CANVAS/)