On Tue, Jul 08, 2003 at 07:14:22AM -0000, Lethalman wrote: > If an admin say this command: '/msg operserv raw > :nickserv join #chan' NickServ join in that chan, ok. > If the command was: '/msg operserv raw : join #chan' > ircd go to SEGFAULT. Why? According to you, the IRC server crashes because ": " is expanded (or, rather, interpreted) as the name of the server. This causes the server to crash, since servers can't join channels and so forth. My question is why any sensible administrator would actually use the RAW command on Services to send such a command to an IRC server. The RAW command does just as it says; it transmits the raw parameter string to the uplink server. This can only be done by Services administrators, who are supposed to be responsible enough not to send strings to the IRC server which will crash it. This "exploit" only seems like it would be usable after the server->server authentication/link process has completed, and therefore presents no risk from users who you do not trust. Your advisory is akin to telling somebody not to stab his friend in the chest with a pitchfork. > Case 1: operserv ordine to a nick (NickServ) to join #chan > Case 2: operserv ordine to server to join #chan > Ircd go to SEGFAULT because it don't find that nick > (eg. hub.server.net). > In fact, if you say: '/msg operserv raw : privmsg #chan > bye' the nick is hub.server.net and not OperServ. > Solutions? > Filter operserv.c in function do_raw or filter ircd > function m_join in s_user.c > > Lethal Lab Member (Lethalman) -- Sean Kelly | PGP KeyID: D2E5E296 smkelly@zombie.org | http://www.zombie.org
Attachment:
pgp00371.pgp
Description: PGP signature
