-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WWSympa crashing on "Malformed UTF-8 character" triggered by malicious hits on do_arcsearch() #1884
Comments
Hi @adam12b1 , |
Additional Note: |
Ah yes, thank you, I ran into that when attempting to test the patch, and got stuck trying to find a FreeBSD package... so I guess we'll need to go with CPAN instead. Will test as soon as I can. |
On our service I can also see a lot of syntax errors in the logs, similar to the above, likely malicious. However, it doesn't seem to have resulted in any crashes. Still recommend installing the above patch? We are running RHEL9. Thanks |
@bboyle262 we haven't seen any more crashes since that first day, but we assume this kind of injection attack will come back at some point in the future, and this protection will be useful then. and @ikedas we have now applied this patch, after installing Unicode::UTF8 via CPAN (we already had Unicode::Normalize as part of the core perl5 package), and WWSympa.fcgi still runs fine. We can't actually tell you if it fixes the problem because we don't know exactly what incoming string was triggering it, but we trust that you have improved the stability of WWSympa, thank you! |
@adam12b1 ok, I'll try to merge the patch above in the next some days. But please let us know here if you see the effect of the patch on your end. Thanks! |
WWSympa: Invalid UTF-8 sequences in input may trigger crashing (#1884)
Version
Sympa 6.2.72
Installation method
FreeBSD port
Expected behavior
WWSympa should filter out malicious traffic so it doesn't cause problems
Actual behavior
WWSympa is crashing, 6 times within 1 hour today, as a result of some kind of malicious probe hitting the archive search page. The last line logged is:
Steps to reproduce
I wish I knew. :( But since this is just some awful malicious probe for vulnerabilities, and the process dies without logging the input string, we have no way of knowing. The best we can do is provide the log lines from some of the other things they're trying, which are getting correctly filtered or blocked and logged, as shown below.
Additional information
Here is the logging for some of the hits before the hit that brings WWSympa down, whatever it might be.
Incident 1:
Incident 2:
Incident 3:
The text was updated successfully, but these errors were encountered: