This bulletin provides a year-end summary of software vulnerabilities that were identified between January 2005 and December 2005. The information is presented only as a index with links to the US-CERT Cyber Security Bulletin the information was published in. There were 5198 reported vulnerabilities: 812 Windows operating system vulnerabilities; 2328 Unix/Linux operating vulnerabilities; and 2058 Multiple operating system vulnerabilities.
It probably counts the same thing in each distribution as its own.
Apache 'Mod_SSL SSLVerifyClient' Restriction BypassApache 'Mod_SSL SSLVerifyClient' Restriction Bypass (Updated) Apache 'Mod_SSL SSLVerifyClient' Restriction Bypass (Updated) Apache 'Mod_SSL SSLVerifyClient' Restriction Bypass (Updated) Apache 'Mod_SSL SSLVerifyClient' Restriction Bypass (Updated) Apache 'Mod_SSL SSLVerifyClient' Restriction Bypass (Updated) Apache 'Mod_SSL SSLVerifyClient' Restriction Bypass (Updated) Apache 'Mod_SSL SSLVerifyClient' Restriction Bypass (Updated) Apache 'Mod_SSL SSLVerifyClient' Restriction Bypass (Updated)
Microsoft Windows ANI File Parsing Errors (Updated) Microsoft Windows ANI File Parsing Errors (Updated) Microsoft Windows ANI File Parsing Errors (Updated) Microsoft Windows ANI File Parsing Errors (Updated) Microsoft Windows ANI File Parsing Errors (Updated) Microsoft Windows ANI File Parsing Errors (Updated) Microsoft Windows ANI File Parsing Errors (Updated)
It'd total bullshit, you can only count vunerabilities in core system componants like the network services and kernel and what's with counting the same ones more than once.
How about this ... get a 1337 haxxor and ask him which system is easier to hack Window$ or Linux (when both are "properly configured") ... I'm betting on Window$. Or put them to the test, see which one is compromised faster, easier.
I dunno, take two identical computers, on one install Window$ on the other Linux, then beef them both up security-wise (harden them), and then get a group of 1337 haxxors and have them hack in remotely. As proof of entry they leave a text document behind or alter some part of the system. Then see which one takes longer to hack.
Ok. If "hardening" meant, both would have firewalls enabled then nobody would ever get into either system. If it meant not enabling a firewall, but disabling all services, then nobody would ever get into either system. In order for the systems to be hackable at all, they would have to be running some sort of daemon.How about IIS6 vs Apache? If it were that, my money would be on Windows/IIS6.