0001687: CRASH w/ GPF or SEGFAULT w/ channel #/dev/null forbid or drop

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001687

Anope Stable (2.0.x series)

[All Projects] General

public

2016-08-17 04:25

2016-09-03 16:40

Reporter

astrutt

Assigned To

Adam

Priority

immediate

Severity

crash

Reproducibility

always

Status

closed

Resolution

unable to reproduce

Platform

3.13.0-24-generic

Ubuntu Linux

OS Version

14.04.5 LTS

Summary

0001687: CRASH w/ GPF or SEGFAULT w/ channel #/dev/null forbid or drop

Description

Anope 2.0.3 crashes when trying to manipulate a channel called #/dev/null

Also channel mode locks don't take effect, on join channel mode says + and nothing more.

Thru operserv forbid, drop causes immediate crash of services. On immediate restart/recovery malicious users who own the channel can create a DoS situation.

Steps To Reproduce

/j #/dev/null
register channel w/ chanserv
as channel founder, drop channel.

Crash.

Thru operserv, using forbid add chan +0 #/dev/null

Crash.

Additional Information

-ChanServ(services@services.XXXXXXXX.net)- Information for channel #/dev/null

kernel: [19244515.364579] services[6044] segfault at 7f62134d78b8 ip 00007f62134d78b8 sp 00007fffaeb97c58 error 15 in libc-2.19.so (deleted)[7f62134d7000+2000]

[Aug 17 03:24:40 2016] ADMIN: used FORBID to add
a forbid on #/dev/null of type chan
[Aug 17 03:24:40 2016] CHANNEL: botserv!bot@irc.net leave #/dev/null
[Aug 17 03:24:40 2016] CHANNEL: destroy #/dev/null

Crash.

Aug 17 03:24:40 xxxxxxxxxxx kernel: [19246454.820054] traps: services[28062] general protection ip:457ccf sp:7ffff915b520 error:0 in services[400000+144000]

Linux xxxxxxxxx 3.13.0-24-generic 0000047-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 14.04.5 LTS

Tags

No tags attached.

Attached Files

Relationships

Notes
(0006809) Adam (administrator) 2016-09-03 16:40	Nothing like this was fixed in 2.0.4, I can not reproduce this bug on 2.0.4 or 2.0.3.

(0006808) astrutt (reporter) 2016-08-17 05:10	Updated to 2.0.4 issue is now non-reproducible. I really wish your release notes would've said something about this for 2.0.4 as I would've updated sooner.

Issue History
Date Modified	Username	Field	Change
2016-08-17 04:25	astrutt	New Issue
2016-08-17 05:10	astrutt	Note Added: 0006808
2016-09-03 16:40	Adam	Note Added: 0006809
2016-09-03 16:40	Adam	Status	new => closed
2016-09-03 16:40	Adam	Assigned To	=> Adam
2016-09-03 16:40	Adam	Resolution	open => unable to reproduce