View Issue Details

IDProjectCategoryView StatusLast Update
0005469unrealircdpublic2019-11-18 08:32
ReporterThe_MythAssigned Tosyzop 
PriorityhighSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
PlatformUnixOSUbuntuOS Version18.04 LTS
Product Version5.0.0-rc1 
Target VersionFixed in Version5.0.0-rc2 
Summary0005469: UnrealIRCd echoing messages that lead Atheme services crash
DescriptionUsing UnrealIRCd 5.0.0-rc1 and Atheme when I've issued the command /OS update, Atheme crashed and I've been forcibly disconnected from the IRCd, probably due to the flood or something.
Steps To Reproduce- Set up UnrealIRCd 5.0.0-rc1 and Atheme services
- /OPER up and do /OS update
- Atheme will crash and you'll be forcibly disconnected (probably due to flood?)
Additional InformationSome lines after executing /OS updated and before being forcibly disconnected:

<@OperServ> James_Bond (James) UPDATE
22:17:23 irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :James_Bond (James) UPDATE
22:17:23 irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :James_Bond (James) UPDATE
22:17:23 irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :James_Bond (James) UPDATE
22:17:23 irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :irc_parse(): got message supposedly from my own client OperServ: :OperServ PRIVMSG #services :James_Bond (James) UPDATE
TagsNo tags attached.
3rd party modules

Activities

syzop

2019-11-18 08:32

administrator   ~0021074

Fixed now, thanks for the report!

commit b88c8ec804c29983e75cc5f43301cb98b497255b
Author: Bram Matthys <syzop@vulnscan.org>
Date: Mon Nov 18 08:16:23 2019 +0100

    Fix sending PRIVMSG back to original sender. This made atheme go
    in a sending loop if you used a services logging channel.
    Reported by The_Myth in https://bugs.unrealircd.org/view.php?id=5469
    The same bug was reported and seemingly fixed before, but wasn't
    actually.

Issue History

Date Modified Username Field Change
2019-11-17 22:28 The_Myth New Issue
2019-11-18 07:42 syzop Assigned To => syzop
2019-11-18 07:42 syzop Status new => confirmed
2019-11-18 08:32 syzop Status confirmed => resolved
2019-11-18 08:32 syzop Resolution open => fixed
2019-11-18 08:32 syzop Fixed in Version => 5.0.0-rc2
2019-11-18 08:32 syzop Note Added: 0021074