It’s very common for open source web applications (as well as some commercial software) to place a “Powered by ____ version x.x.x” notice on publicly accessible pages. Other than advertising purposes, there is little or no reason to disclose this information. While some license agreements require that the notice stay visible, you can usually remove the specific version number and stay compliant. If not, talk to the vendor - you shouldn’t have to give away your specific implementation details to the world.
So why is this an issue? Because it allows for easy enumeration of vulnerable sites using Google and other search engines. This type of reconnaissance is completely passive and easy enough for any script kiddie to do. When a new vulnerability is announced for Coolblogprogram v1.2.3, you better believe there will be script kiddies all over the world searching Google for “Powered by Coolblogprogram v.1.2.3″. Scripts for mass exploitation can easily be written when it’s that easy to get a list of vulnerable sites.
Have you been hacked through a popular web-based application? Check your traffic statistics for search engine queries - there’s a good chance, if it was a common exploit, that someone just searched for the vulnerable version number and found your site, or that a bot did the same.
Unless you have a really compelling reason to tell all your visitors exactly what version you are running, I highly recommend removing the version number from all publicly accessible web pages. This can be easily done by editing the header and footer templates of most web-based software. While this may not stop a determined hacker from figuring out what you’re running, it cuts down on the script kiddies that love to mass exploit and deface sites running popular web apps.
These notices are usually found in the following places:
1. Web site footer - near the copyright notice at the bottom
2. Title tag
3. Meta tags - such as generator, description, and keywords
4. Other locations. Run a find or grep on the HTML source to see if there are any hidden notices.
Disclaimer: I don’t recommend “security through obscurity” (of which this is an example) as an effective security approach. However, with the plethora of spam bots, wannabe google hackers, and script kiddies - using this technique of anonymizing your web-based applications could save you a lot of trouble, and reduce the malicious traffic you receive. Just keep in mind that ultimately, the application is still just as vulnerable as it was before.