-
Notifications
You must be signed in to change notification settings - Fork 102
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
"Hacker" script poking at wwsympa generates lots of email to listmaster. #1244
Comments
This poking also broke logins to wwsympa using sso_login until I restarted it. wwsympa presented a half a dozen different login boxes instead of the two that you normally see at: https://lists.cam.ac.uk/sympa ("Login using Raven" (our SSO service) and "Login locally"). I'm rather alarmed that random poking can break logins: there would appear to be security implications. It looks like all login attempts using SSO were broken from 08:30 to 10:24 when I restarted wwsympa, about 400 legitimate logins attempts in total. A legitimate login attempt while in this broken state generated the error below.
|
generates an error message to listmaster |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@dpc22, can you please submit separate issue on the latter problem (broken sso_login attempts)? |
Will do, although I think that they are actually two different manifestations of the same problem. |
The PR above contains the fix for this issue (especially d067d9c). This will be included in the next beta. |
Version
6.2.66
Installation method
My own RPM, derived from "offical" RHEL rpm
Expected behavior
wwsympa shouldn't generate notification emails to listmaster just because an unknown Web client submitted a HTTP GET or POST with invalid parameters: that is outside our control.
Actual behavior
Someone in China fired up a script which attempted random SQL injection attacks against wwsympa: I don't have evidence of a targetted attack.
We received 429 "Listmaster: internal server error" messages this morning in the space of 20 minutes, until I blocked the IP address in question.
I think that these are largely linked to do_sso_login() with a random nonsense value for the authentication service parameter ("bxss.me"/"2on0943dg8uk.php"). There is an awful lot of "not conform to regex", but I hope those aren't generating emails.
Here are two examples:
The text was updated successfully, but these errors were encountered: