Closed mmatthiesencsc closed 8 years ago
Good catch. This error it is very easy to reproduce by visiting:
http://your_metashare_node/stats/top/?view=random_thing
In this case you have posted, some malicious user (probably a bot, don't assume you are targeted) was trying to use view=%00swhdny
hoping that the 00 byte in the request could crash the system, reveal critical information from the server or allow some door to open (I am not a security expert, I don't know much about these things). This is proof that there is (bad) people out there looking for exploits to use, and shows why upgrade meta-share dependencies to use supported versions is important. If a severe exploit appeared for django 1.3, there are no security upgrades to protect us from it, because django-1.3 is not supported anymore. There is no need to panic, but there is a real need to do something about it.
As for the patch, I believe that setting geovisits = []
will make the World map shown in the statistics page appear grey, without any visit from any country, which is totally fine in this case. The patch is already appended to the pull request #758.
Best,
Hi Sergio, Thanks for your feedback!
I tested your URL on http://metashare.csc.fi/stats/top/?view=random_thing and found that another variable is not initialised: visitstitle So I set a default there as well: visitstitle = "Unknown"
And now Metashare does not crash anymore. Case closed, I'd say. As for django 1.3, an upgrade there must be decided way above our pay grade. I hope Metashare gets some funding.
Hi,
Sometimes Metashare crashes and throws an error like below. The root cause seems to be