]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002846.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 002846.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] /ns ghost exploit
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/ns%20ghost%20exploit&In-Reply-To=">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="002845.html">
11 <LINK REL="Next" HREF="002847.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] /ns ghost exploit</H1>
15 <B>Mark Hetherington</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/ns%20ghost%20exploit&In-Reply-To="
17 TITLE="[IRCServices] /ns ghost exploit">mark at ctcp.net
18 </A><BR>
19 <I>Thu Mar 14 12:27:01 PST 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002845.html">[IRCServices] /ns ghost exploit
22 </A></li>
23 <LI>Next message: <A HREF="002847.html">[IRCServices] What is wrong?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2846">[ date ]</a>
27 <a href="thread.html#2846">[ thread ]</a>
28 <a href="subject.html#2846">[ subject ]</a>
29 <a href="author.html#2846">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i> Andrew Church wrote
35 </I>&gt;<i> Services does not use SVSKILL in the first place,
36 </I>
37 Sorry, my mistake. I meant Services will issue a kill for that user.
38
39 &gt;<i> and
40 </I>&gt;<i> does not allow
41 </I>&gt;<i> GHOST anyway without a password unless the calling user is on
42 </I>&gt;<i> the access
43 </I>&gt;<i> list of the target nick _and_ the nick does not have the
44 </I>&gt;<i> SECURE option set.
45 </I>
46 I know this. It still does not prevent a user using services to kill
47 another user just because they happen to use their nickname.
48
49 Nick A register A and also registers or links B, C, D, E.
50
51 A new user connects using nick B and would get the usual warning from
52 services. However, before they have the opportunity to choose a new
53 nickname, A who is identified and has the password for B issues /ns ghost B
54 password either manually or from a script which kills that user from the
55 network. I didn't highlight a problem with the way services checks a users
56 right to issue the command, merely in the way that the command is open to
57 abuse.
58
59 &gt;<i> Have you modified Services?
60 </I>
61 No.
62
63 Mark.
64
65 &gt;<i>
66 </I>&gt;<i> --Andrew Church
67 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
68 </I>&gt;<i> <A HREF="http://achurch.org/">http://achurch.org/</A>
69 </I>&gt;<i>
70 </I>&gt;<i> &gt;Something I recently became aware of was users &quot;abusing&quot; the
71 </I>&gt;<i> ghost command.
72 </I>&gt;<i> &gt;
73 </I>&gt;<i> &gt;When the ghost command is issued, Services will SVSKILL the
74 </I>&gt;<i> user from the
75 </I>&gt;<i> &gt;network. However, the new trend appears to be setting up a
76 </I>&gt;<i> notify script,
77 </I>&gt;<i> &gt;which will automatically ghost any user trying to use a
78 </I>&gt;<i> given nickname.
79 </I>&gt;<i> &gt;This quickly became popular. How this came to my attention
80 </I>&gt;<i> is that a new
81 </I>&gt;<i> &gt;user was trying to access the network but was repeatedly
82 </I>&gt;<i> killed by the
83 </I>&gt;<i> &gt;ghost command.
84 </I>&gt;<i> &gt;
85 </I>&gt;<i> &gt;Use of &quot;kill immediate&quot; should be sufficient for those users
86 </I>&gt;<i> who do not
87 </I>&gt;<i> &gt;want people using their nicknames and can be handled by
88 </I>&gt;<i> services with a
89 </I>&gt;<i> &gt;nick change so I do not see use of the command in this manner as
90 </I>&gt;<i> &gt;beneficial.
91 </I>&gt;<i> &gt;
92 </I>&gt;<i> &gt;One way to remove this exploit which seems the least complex
93 </I>&gt;<i> to actually
94 </I>&gt;<i> &gt;manage is to only trigger the ghost if the target is
95 </I>&gt;<i> currently identified.
96 </I>&gt;<i> &gt;
97 </I>&gt;<i> &gt;This would mean that in the event a user got disconnected
98 </I>&gt;<i> before they were
99 </I>&gt;<i> &gt;able to identify, they would be unable to remove a real 'ghost' on
100 </I>&gt;<i> &gt;reconnect with the ghost command, but they could use 'recover'
101 </I>&gt;<i> &gt;and 'release' instead. I believe that the 'recover' will
102 </I>&gt;<i> &quot;guest&quot; a user
103 </I>&gt;<i> &gt;where NSForceNickChange is enabled.
104 </I>&gt;<i> &gt;
105 </I>&gt;<i> &gt;--
106 </I>&gt;<i> &gt;Mark.
107 </I>
108 --
109 Mark.
110
111
112
113 </PRE>
114
115 <!--endarticle-->
116 <HR>
117 <P><UL>
118 <!--threads-->
119 <LI>Previous message: <A HREF="002845.html">[IRCServices] /ns ghost exploit
120 </A></li>
121 <LI>Next message: <A HREF="002847.html">[IRCServices] What is wrong?
122 </A></li>
123 <LI> <B>Messages sorted by:</B>
124 <a href="date.html#2846">[ date ]</a>
125 <a href="thread.html#2846">[ thread ]</a>
126 <a href="subject.html#2846">[ subject ]</a>
127 <a href="author.html#2846">[ author ]</a>
128 </LI>
129 </UL>
130
131 </body></html>