I come across a few web sites with errors or issues and normally I’ll eventually find somebody to report those errors to and some are great, will fix and thank you, others will just fix and some never bother and their sites still have issues but the vast majority are not so piss poor secure I just move on. I don’t need to be thanked just for them to fix their sites.
So over a month ago (may 2018) I came to https://www.jointwastesolutions.org so I could sign up for green waste collection, all pretty mundane until I tried to register on the redirect at https://jointwastesolutions.amcsgroup.com and it threw an error. Of course anybody who has ever worked with Windows, IIS and ASP.NET the first thing you should do is make sure custom errors are turned on, indeed they are now by default so somebody has gone out of their way to make the site less secure.
The main reason for turning on custom errors is that without your site exposes information. In this case we can see that the site is running ASP.NET v4.6.1 which is currently 4 version out of date. It also shows that the server is using Windows 2012 which is “End of Life” in October 2018. So outdated software on a server running a nearly EoL operating system. A quick scan of the server shows it may not have been rebooted for over 400 days – so no Windows Updates !!!
Nothing has been done to even remotely secure the server which leaves it open to all sorts of compromises e.g. cross site scripting. As you can see this cloud based server fails miserably.
But at least it’s using SSL I hear you cry…. yes but much like the proverbial chocolate fireguard it’s so poorly configured as to make it almost pointless. It still uses SSL v3, is vulnerable to DROWN and POODLE, supports piss weak encryption. Now I never got as far as being able to put in credit card details or even bank details but this is clearly not PCI-DSS compliant.
You’d think that a company would be happy for somebody to quietly point out their errors but so far other a month I’ve been told by Amey’s social media team that they would pass on the information, and when nothing happened they just ignored me. Surrey Heath Borough Council originally told me as this was reported before 25th May 2018 it was not covered by the GDPR !!! So I emailed both data protection officers with the information and Amey have yet to reply and SHBC have sent two holding emails.
I’m still trying to get to the ICO https://ico.org.uk but they seem very busy – let’s hope somebody else doesn’t or hasn’t found this childishly comically configured server. Personally I’d treat the server as compromised but then I’m averagely good at my job.