Comment the story smells (Score 0) 203
So, Apache, with a larger market share (66%, ?) has been the server serving the application which was hacked/defaced. That is news how? For example when facebook was broken into and the private images downloaded and put up on torrents, Apache was probably serving the files but not the vulnerable point!
Lets look at it this way, if there is such a wave of defacements, how come whitehouse.gov which runs linux/freebsd and Apache, how come they arent getting defaced? Because someone serious took the time to configure the damn server properly. How hard is that? google->hardening apache. then use common sense when handling input in your applications/scripts.
facebook@netcraft Apache/1.3.37.fb1
".fb1"? how customised do you suppose fb1 is? If it were defaced, would it be apache's fault, a 0day exploit perhaps, or due to the configuration (or "fb1" whatever that means, if anything)?