Slashdot Mirror


Linux/Unix Tops Charts for Vulnerabilities in 2005

BeanBunny writes "I realize that this topic is almost as volatile around here as Intelligent Design, but I think this is interesting nonetheless. US-CERT has released their year-end vulnerability summary. According to InformationWeek.com, Linux/Unix (including Mac OS) had almost three times the number of OS-specific vulnerabilities reported last year compared to Microsoft Windows. Obviously, statistics are meaningless without the proper conjecture, speculation, and opinionation, so let the debate begin again over which OS is really more secure."

86 of 438 comments (clear)

  1. One Take by ackthpt · · Score: 5, Insightful
    It's because most *ix vulnerabilities are reported (and usually fixed rather quickly, particularly in the case of Linux distros.)

    Who knows how many Windows vulnerabilities there are known to Microsoft? Can you say "Vested Interest"? They certainly have tried to have divulging them criminalized as an act against national security, never mind warning customers of all sizes that they may have been compromised while Microsoft fiddled away at a patch for the past six months.

    I take this sort of revelation with a grain of salt and give it as much weight.

    many eyes only make for strong code when the code can be seen

    --

    A feeling of having made the same mistake before: Deja Foobar
    1. Re:One Take by LordNightwalker · · Score: 2, Interesting

      Not only that; the comparison is Linux/Unix including MacOS... How many kernels are we talking about here? There's the Linux kernel, 3 different BSD kernels, the MacOS kernel based on BSD (I assume it's different enough to count as a separate kernel, don't really know), HP-UX, AIX, SCO Unixware, Solaris (just check the vulnerability list) and probably some other Unix variants I forgot to mention compared against one OS. Yeah, sure, there's different Windows versions out there, but all Windows XP "distros" are based on the same kernel, with some "advanced" features compiled out of configed out...

      Even assuming they're not just counting Windows XP vulnerabilities, but also the ones found some of the other Windows versions that are still in use, it's still a shitload of unix variants compared to a small amount of Windows versions. Fair comparison indeed. Doing statistics like this could even make the Ford Pinto look safe. After all, the number of deadly incidents involving a Ford Pinto pales in comparison to the number of accidents involving all other brands and models if you add them up.

      Other than that, just look at the damn report... Most bugs aren't even OS bugs, but bugs in third party software. How the hell is a bug in Acrobat Reader, 3Com 3CDaemon, F-Secure Antivirus or Platinum FTP Server MS's fault? If you look at it like that, of course you're gonna find a lot more bugs in the linux/unix category: there's simply a lot more software for those OS's. Your average Linux distro has more unique applications on board than most people would ever install on a Windows box, and a lot of it is indeed of dubious quality because it simply wasn't written with security in mind. Just like all that shareware crap for Windows.

      I don't question the validity of the report, but I do question the journalistic integrity of the people reporting this. This is a list of application vulnerabilities broken down per OS, where OS is one of the following: "Windows" and "Other"; not some measure of the security of the OS's in question. Heck, lots of stuff on the Windows list is dubious software I wouldn't wanna install on my box anyway. Exeem? Chris Moneymaker's World Poker Championship? Crazy Browser? Optimal Desktop? Heck, add every piece of malware to the list and count it as an "insecure application" while you're at it.
      --
      Install windows on my workstation? You crazy? Got any idea how much I paid for the damn thing?
    2. Re:One Take by skraps · · Score: 4, Funny

      You feel that sting, big boy, huh? That's pride fuckin' with you!

      (source)

      --
      Karma: -2147483648 (Mostly affected by integer overflow)
  2. perfect place to discuss, though! by yagu · · Score: 4, Insightful

    It may be a volatile topic, but where better to discuss the reality, validity, etc., of these purported vulnerabilities?

    Get your education here (hopefully) so you can address the confrontations at work, from your friends, etc. when they accuse you of evangelizing an OS more vulnerable than Windows!

    Look for answers to:

    • how these vulnerabilities are reported (the article is painfully light on this)
    • what the vulnerabilities were and how serious they were
    • whether or not there is redundancy in the reporting mechanisms
    • what association and influence Microsoft has over this reporting process
    • how quickly vulnerabilities are fixed and how soon working patches are made available to the public
    • who is the author of this article? (Gregg Keizer), and what is his slant/bias?

    I'm sure this is a partial list, and I don't know the answers to these points, but I'd like to.

  3. From the FA: by drinkypoo · · Score: 4, Insightful

    The end-of-year vulnerability score should be taken with a grain of salt, however, since US-CERT doesn't filter out updates (so one actual vulnerability can be counted numerous times) nor does it break out individual vulnerabilities from warnings that cover multiple bugs (as in the many Mac OS X vulnerability listings).

    In other words, these findings are absolutely useless.

    Also, even if they DID filter out updates and break out individual vulnerabilities, you would still have to know for how many days each vulnerability remained unpatched to have any useful information.

    As this oh-so-well-written website told me the first time I clicked on this story, "Nothing to see here. Move along."

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  4. Whats funny is by Anonymous Coward · · Score: 2, Insightful

    That they listed a few PHP apps that work on all 3 OS's as only on Linux. Hmmm

  5. Along with the total numbers... by Jane_Dozey · · Score: 4, Insightful

    ...they really should take into account severity, time until a fix was avaliable (from the time of discovery and not just disclosure to the public) and if the vulnrability was actually IN the OS or whether it was a third party app. Then perhaps the total numbers will start being a little more helpful.

    --
    Silly rabbit
    1. Re:Along with the total numbers... by LnxAddct · · Score: 5, Informative

      Not only do they not take into account severity, a large portion of the vulnerabilites in the Linux list are tagged with "update" meaning that a large portion are just updates to previously filed bugs, but worst of all, their lists are just plain wrong. A huge chunk of the open source projects listed under *nix are not listed under Windows, yet they run on Windows and the vulnerabilities affected windows. There are Apache, Gaim, PHP, Zope, Clam AV, Vim, Emacs,Perl, MySql and many more vulnerabilities listed just under *nix, yet equally affect Windows. Even worse, Windows has 1 firefox vulnerability listed, yet *nix has 153 firefox vulnerabilities listed (including the couple of tens of updates) but every vulnerability I saw listed equally affected Windows. This list is separating vulnerabilities by pretty much whether its open source or not (for the most part, say 90%), not by what platform it runs on, yet the latter is how they are categorized. This whole list is a big giant piece of misinformation and someone needs to correct it.

      It's also not intelligent to group together all Unix derived operating systems, as they all follow completely different security structures, development paradigms, and grouping them is simply serving to inflate already misleading numbers. The fact is that the only thing this list clearly shows is that open source projects are much better at following up on security problems(noting all of the updates), and that there are far more applications that run under *nix than under Windows once you account for all of the at least semi-popular open source projects.
      Regards,
      Steve

  6. Dupe by A+beautiful+mind · · Score: 2, Informative

    Sigh. The statistics were flawed the first time they were posted to /., no need to repeat that bag of bad science.

    --
    It takes a man to suffer ignorance and smile
    Be yourself no matter what they say
  7. Already hashed over in depth on GrokLaw by jmac880n · · Score: 5, Informative

    This is old news. PJ has done a pretty thorough job debunking this one on Groklaw.

    1. Re:Already hashed over in depth on GrokLaw by jmac880n · · Score: 3, Insightful

      Now PJ is a security expert?

      No. But she has access to a lot of people who are very informed.

      It's amazing what the community can do when organized by a good leader.

  8. Cause it's a dupe? by goombah99 · · Score: 3, Informative

    Nothing new here that was not reported on slashdot four days ago.. Move along. or repost your incitefule or insightful comment. or someone elses if you karma whore.

    --
    Some drink at the fountain of knowledge. Others just gargle.
  9. Vulns you won't see listed by SilverspurG · · Score: 2, Insightful

    In the Microsoft section there could be an entire block for : "Clueless user -- installed malware X which caused the propagation of virus Y"

    In the Linux section there would be a similar block for : "Clueless user -- caused hard drive format"

    Yeah. That was wanton. Sure, okay. I agree. It's probably true that most OSS vulns are reported to public forums while most MS vulns probably get identified in house and rolled into a patch. Maybe. In 6 months or so after the devs have had fun with it for a while.

    --
    fast as fast can be. you'll never catch me.
    1. Re:Vulns you won't see listed by jguthrie · · Score: 2, Interesting

      On my computers, /dev/hda is owned by root.disk with permissions of 660, and none of these computers has any real users in the disk group. So, it doesn't matter if I try it at home or not, it's not going to do anything. I suppose that if I routinely ran as root, it would be different, but I don't and it's not.

  10. the thing about the list.... by User+956 · · Score: 2, Informative

    If you read the actual list, a lot of the vulnerabilities are listed multiple times with an (updated) notation. So the 2,328 number isn't exactly "correct".

    --
    The theory of relativity doesn't work right in Arkansas.
    1. Re:the thing about the list.... by beacher · · Score: 2, Interesting

      Okay I "uniqued" it by removing the (Updated)'d and it came out to 1048 - I know this isn't a good # because I didn't review if these were multiple platforms, or if they were seperate incidents within a software package...

      Top 10 by bugs listed -
              * GNU GZip Directory Traversal 13
              * Multiple Vendors LibXPM Bitmap_unit Integer Overflow 13
              * Multiple Vendors Linux Kernel Multiple Vulnerabilities 13
              * GNU GZip File Permission Modification 12
              * Gzip Zgrep Arbitrary Command Execution 12
              * LBL TCPDump Remote Denials of Service 12
              * PCRE Regular Expression Heap Overflow 12
              * BZip2 File Permission Modification 10
              * GNU Xpdf Buffer Overflow in doImage() 10
              * Multiple Vendor Zlib Compression Library Decompression Remote Denial of Service 10

      I was particularly surprised to see that Gentoo, RedHat and SuSE, Debian had roughly under 10 problems with their distro specific code (portage, Yast, sysreport)

      It looks like there was a half assed attempt to categorize the bugs as "Multiple Vendor" and then someone gave up on it, or else someone wasn't really consistent with the counting strategy...

      -B

    2. Re:the thing about the list.... by SilverspurG · · Score: 2, Insightful

      This isn't about making numbers meaningful. This is about discussing the topic.

      The proper thing to do if someone wants to argue about whether or not the inaccuracies are technically balanced is to categorize them (multiple listings, updates, more than one OS in Linux, 3rd part apps) and then ask them to be moot or, if that's denied, cede them outright.

      Then you can move on to the real topics... if there are any left.

      --
      fast as fast can be. you'll never catch me.
  11. Oh good grief... by aggieben · · Score: 2
    go troll somewhere else. This has been discussed repeatedly everywhere on the internet, and the it only only ever proves two things:
    • is that everyone is already has an opinion on the issue and isn't going to change it.
    • these opinions are hardly ever based on emperical evidence
    --
    Don't become a regular here, you will become retarded. -- Yoda the Retard
  12. One possible take by El+Royo · · Score: 2, Insightful

    It would be interesting to compare the number of different versions of software and applications this covers. Windows XP has not evolved tremendously in the last several years. Certainly Microsoft has shown a renewed (if not a completely successful) focus on security lately. But I think Microsoft benefits in this survey from a more stately release cycle.

    --
    Author of Enyo: Up and Running from O'Reilly Media
  13. Yes, indeed. by DaedalusHKX · · Score: 5, Insightful

    Let me put this into context.

    Linux (Red Hat to be specific) reported AND HAD ALREADY fixed similar JPG/GIF/PNG flaws more than 2 years before microsoft ACKNOWLEDGED that they had similar flaws. It may have been the same bug, or not, but still, similar bugs, FAR different timetables. And these are both companies right? One did base itself on code that it didn't try to lynch you for viewing, modifying or making your own. Hint: it wasn't microsoft.

    --------------

    What does it take for open source (being open to all) to report a flaw?

    Finding it of course.

    What does it take for a huge software house with stock to shill... errrr.. sell (since product sales do not a stock value raise anymore).

    Reporting few security flaws. "Proving" successful implementations are the norm... (via bought studies of course, and occasional true stories, if they ever are unbiased).

    --------------

    And of course, having worked inside an IT house, I'm quite familiar with how they work... especially M$ partners. I've never seen a SINGLE one ever report a vulnerability... whether our fault or the customer's or anyone's. Until it was fixed, or exploited, we NEVER EVER reported them... standard policy.

    ~D

    --
    " What luck for rulers that men do not think" - Adolf Hitler
    1. Re:Yes, indeed. by ajs318 · · Score: 3, Interesting

      While I don't doubt that many desktop and laptop Linux / unix systems may well be running libpng, these systems most probably will be on the wrong side of a NAT box for anyone to get at them. Servers most probably won't be running X at all -- and therefore will have no need of libpng.

      On a unix system, if you find something, anything, with serious enough flaws, often you can just rm it or chmod -x it until a new version is available. It'll break some things, for sure; but you have to weigh up whether the ability to display PNG images is worth more than the inability for third parties to run arbitrary code on your box {and the answer to that most probably depends on whether the system is a desktop or server}.

      Anyway, the figures hardly surprise me. Everyone has access to the source code for Linux and BSD, so there are more people in a position to spot problems there {and good guys by definition outnumber bad guys}; and nobody has anything to lose from the existence of a vulnerability as long as it gets patched. But only a select few have access to the source code for Windows, and Microsoft have their own reasons for not wanting vulnerabilities to be disclosed to the public. Also, unix users seem generally to be more interested in what goes on beneath the bonnet -- and therefore more likely to apply patches in a timely fashion.

      --
      Je fume. Tu fumes. Nous fûmes!
    2. Re:Yes, indeed. by The_Spud · · Score: 2, Insightful

      lib png will indeed be on many servers which do image processing as part of serving web pages. I think, but i could be wrong, that both the gd image library thats part of php and image magick use libpng for handling png files.

      On production machines you can't just delete or disable the library and go oh well we can't serve the images that make up a large part of the site. thats too bad.
      Everyone has access to the source code for Linux and BSD, so there are more people in a position to spot problems there

      While it is true more people have the opertunity to go through the source and check for problems, how many actually do? Did you read throught the source for any of the open source software you installed ? I certainly don't have the time and in many cases enough knowledge of the language and problem to properly review the code.

      I never been that convinced by the Cathedral vs the Bazaar argument. Given fewer people use linux and of those users even less will have enough knowledge, time and expertise to bug hunt in any meaningful way is having the source open that much of an advantage?

      I think the real advantage is the comunity around the OSS movement as I was having a problem with firewire under linux and was able to get in contact with one of the authors of the drivers who helped fix the problem.

    3. Re:Yes, indeed. by ajs318 · · Score: 2, Insightful
      Not every web server processes images with imagemagick or gd -- and you don't need libpng just to serve them up statically. Just generating images on the fly, or even composing based on known good images kept on the server, would be safe anyway -- the exploit as I have seen it described required a deliberately malformed image as input. You would have to have a web application capable of loading arbitrary images via HTTP and doing some operation on them {perhaps overlaying a caption or copyright message, or drawing on comedy genitals}, in order to be vulnerable. In which case, taking it offline for an hour or so whilst patching and recompiling libpng might be a small price to pay {I expect Windows/IE users probably are used to web sites not displaying properly anyway; when I used Windows, I never really knew what was up with it, but rebooting usually fixed it so I never worried too much}.
      Did you read throught the source for any of the open source software you installed ?
      Some of it. Not all of it, but probably about my fair share. And I feel much more inclined to trust my distro's packaging team {who are accountable to a large community of experienced hackers, and do read all the source code of everything they compile}, than to trust some pedlar of "free" closed binaries {if they won't show me the source code, then what are they hiding from me?}.
      Given fewer people use linux and of those users even less will have enough knowledge, time and expertise to bug hunt in any meaningful way is having the source open that much of an advantage?
      Yes it is. There are times when access to the source code is essential. The rarity of such occasions does not diminish the usefulness of the source code if and when they arise: you have a sample size of one if the situation does arise, or nil if it doesn't, and either way that is way too few data points to be statistically significant.
      I think the real advantage is the comunity around the OSS movement as I was having a problem with firewire under linux and was able to get in contact with one of the authors of the drivers who helped fix the problem.
      You seem to be forgetting that this comunity [sic] contains many people who do read source code.
      --
      Je fume. Tu fumes. Nous fûmes!
    4. Re:Yes, indeed. by The_Spud · · Score: 2, Interesting

      the exploit as I have seen it described required a deliberately malformed image as input. You would have to have a web application capable of loading arbitrary images via HTTP and doing some operation on them {perhaps overlaying a caption or copyright message, or drawing on comedy genitals}

      How about a content management system that creates thumbnails or automatically resizes images, e.g. ebay image galleries or myspace ?


      In which case, taking it offline for an hour or so whilst patching and recompiling whilst patching and recompiling libpng might be a small price to pay

      It is a big deal to take a production server down for an hour and it could cost major money to do so.


      Yes it is. There are times when access to the source code is essential. The rarity of such occasions does not diminish the usefulness of the source code if and when they arise: you have a sample size of one if the situation does arise, or nil if it doesn't, and either way that is way too few data points to be statistically significant.

      This doesn't actually counter my point. You stated that there are occasions on which it is useful or even vital to be able to have the source code for software. Completely agree. This doesn't contradict the point I was trying to make that having the source available to everyone doesn't necessarily increase the amount of bugs found given the limited number of people actually have the time and expertise to look through the code.?

      You seem to be forgetting that this comunity [sic] contains many people who do read source code.

      Of this 'many' what proportion actually could understand something complex and specialist such as the kernel or the image processing internals of the gimp for example ?

      Out of interest what software did you read the source for and have you ever actually found any flaws

    5. Re:Yes, indeed. by Serpent+Mage · · Score: 2, Interesting

      Out of interest what software did you read the source for and have you ever actually found any flaws

      Well since you are asking I found a place in the gtk (1.2) clipboard monitor code that had a potential for buffer overflow due to not using the glib wrappers for a pointer initialization.

      I've also accidentally traced down a problem that I thought was in the eclipse swt 3.1.1 api down to a firefox memory overflow with closing open tabs with content in the clipboard (which was fixed up in 1.5 never checked to changelogs to see if it was retrofitted into the 1.0.x series though and don't care)

      I helped out with evolution when it was still in the "how the heck do you even compile this crap" phase and found a couple of flaws as well. Of course nothing in there was really good code at the time and being that it was like 90% hacks in lots of places at that time, that may or may not count.

  14. How about pointing out... by Anonymous Coward · · Score: 5, Insightful

    They're lumping Linux, UNIX, BSD, and OS X together and saying they together had more vulnerabilities than any single version of windows...

    I'm sure all the GM, Toyota and Honda cars between 1970 and 1990 put together had more design flaws than the Ford Pinto, but this comparison is not relevant.

    1. Re:How about pointing out... by molnarcs · · Score: 5, Insightful
      Yeah, I agree.

      In other words:

      There are at least 12 distinct operating systems in their list - Solaris, Cisco, SCO Unixware, OpenBSD, FreeBSD, NetBSD, HP-UX, AIX, HP Tru64, MacOS X, Linux variants like SuSE, Debian, Gentoo, RedHat (I counted Linux as one, even though most of the vulns. are found in their specific configuration/management tools). Add an arbitrary number of applications: KDE and GNOME, that in itself has more apps that are counted for Windows, every free SQL database server, mail server, (LotusDomino for Christ's sake!), imap client, ftp client, ftp server, etc...

      Now we have a comparison of a single operating system (Windows) + apps running on it with at least 12 distinct operating systems + 10x the number of apps that was counted for windows. The result is rather surprising: there are JUST 4x more bugs in 12 operating systems + 10x more apps than in windows + windows apps alone! This result is much more unfavorable for Microsoft than to any Unix/Linux OS!

      Of course, the fallacy of the comparison is that it suggests that Linux or Unix is an Operating System. For someone who does not look at the details, it might seem that installing a specific Linux or Unix operating system is more risky - hey, there are more bugs found in Linux/Unix, that's what the article says! In fact, the opposite is true, if you look at the details.

      Not that the comparison is useful in any way - why are Safari bugs counted at all? Safari runs on OS X only, so you can't just dump safari bugs into linux/unix bugs category (how retarded is that?). Why are bugs found in SuSE YAST counted as Linux bugs? They have nothing to do with linux or unix - they are specific to one operating system: SuSE linux (the same applies for all the bugs counted in Debian, RedHat, Gentoo, etc.) Not to mention the duplications: Eric Raymonds "Fetchmail POP3 Client Buffer Overflow" is counted 5 times for linux and BSDs. There are duplications for windows as well though. In other words, this list or comparison is pretty much unusable.

    2. Re:How about pointing out... by qub333 · · Score: 2, Interesting

      and more over, these were not just *nix vulnerabilities, they were *nix apps. If we included every security flaw in every program that runs on windows this year I feel that ths list might grow a bit......

      --
      Kevin
      http://kubasik.net/blog/

    3. Re:How about pointing out... by Anonymous Coward · · Score: 2, Funny

      don't be bad mouthing the Pinto!

      LMFAO! To a Portuguese speaker this is mighty funny!

      Hint: "Pinto" means, among other things, dick in Portuguese...

    4. Re:How about pointing out... by Vicissidude · · Score: 3, Insightful

      Now we have a comparison of a single operating system (Windows) + apps running on it with at least 12 distinct operating systems + 10x the number of apps that was counted for windows. The result is rather surprising: there are JUST 4x more bugs in 12 operating systems + 10x more apps than in windows + windows apps alone! This result is much more unfavorable for Microsoft than to any Unix/Linux OS!

      To be fair, Windows is not the monolithic program you suggest. Windows NT is different from Windows 98. Windows 98 is different from Windows ME. ME is different from 2000. 2000 is different from XP. XP is different from 2003. Each has a similar, but different, code base with their own bugs.

      To Microsoft's advantage, Window's code similarity means that a bug found in Windows 2003 can be traced and squashed in Windows 2000 and XP. This results in the bug being removed in all flavors of Windows simultaneously. However, that would be impossible with the various *nixes.

      Either way, I agree with Mark Twain. There are lies, damned lies, and statistics.

    5. Re:How about pointing out... by miyako · · Score: 2, Informative

      It may be impossible for the various kernels, but I would bet that it's actually easier to patch a lot of things in *nix than in windows because the *nix kernels doesn't throw things like a web browser or a window manager into the kernel.
      If there is a security hole with Konquror browsing files on KDE then KDE issues a patch and it should mostly work on all of the various systems it runs on.

      --
      Famous Last Words: "hmm...wikipedia says it's edible"
    6. Re:How about pointing out... by Pollardito · · Score: 4, Informative
      it's even worse than that, here's some of the UNIX vulnerabilities :
      # Adobe Acrobat Reader mailListIsPdf() Buffer Overflow (Updated)
      # Adobe Acrobat Reader mailListIsPdf() Buffer Overflow (Updated)
      # Adobe Acrobat Reader UnixAppOpenFilePerform Buffer Overflow
      # Adobe Acrobat Reader UnixAppOpenFilePerform Buffer Overflow (Updated)
      # Adobe Reader / Acrobat Arbitrary Code Execution & Elevated Privileges
      # Adobe Reader For Unix Local File Disclosure
      # Andrew Church IRC Services LISTLINKS Information Disclosure
      this isn't a list of OS vulnerabilities, it's a list of application vulnerabilities sorted by OS
    7. Re:How about pointing out... by Dolda2000 · · Score: 4, Informative
      Now we have a comparison of a single operating system (Windows) + apps running on it with at least 12 distinct operating systems + 10x the number of apps that was counted for windows. The result is rather surprising: there are JUST 4x more bugs in 12 operating systems + 10x more apps than in windows + windows apps alone! This result is much more unfavorable for Microsoft than to any Unix/Linux OS!
      Actually, it's far worse than that. If you filter out the "Updated" entries for each vulnerability, it lands on 672 for Windows and 892 for the so called "Unix/Linux" category, which means a mere 32% more vulnerabilities for 12 systems + 10x more apps than in Windows + Windows apps alone!
    8. Re:How about pointing out... by linuxfanatic1024 · · Score: 2, Insightful

      The point of the GP's post is that Windows integrates all that stuff into the operating system, while on Linux/Unix systems it is a distinctly separate part. You can't run Windows without the GUI, but you CAN run Unix systems without the GUI.

      --
      Microsoft-free since March 28, 2004
    9. Re:How about pointing out... by Zerathdune · · Score: 3, Insightful

      ok granted. however, if you're going to count each windows OS as a separate OS, you also, in maintaining fairness, have to count each linux distro as a separate OS. maybe the same with OSX, I'm not familiar with the platform so I don't know how different the 4 versions have been. in any case, if you break it out that far, you're dealing with several hundred unix/linux OS's with 10 times (at least) as many apps, vs just a handful of windows OS's.

      --
      No single raindrop believes that it is responsible for the storm.
    10. Re:How about pointing out... by jrockway · · Score: 4, Insightful

      The security holes don't even have anything to do with the OS. When there's a Windows hole, it's a hole that allows you to take over the OS. These "linux holes" are holes in shitty php scripts that happen to run on Linux. This just in... you can write shitty, insecure software that runs on Linux. Duh!

      If you look at all holes in the Linux kernel and base GNU utils vs. all holes in the Windows kernel and in the Windows core OS, you'll notice that Windows has many, many more. And the ones that Linux has are things like "temporary file permissions vulnerability" whereas Windows has ones like "arbitrary user from the network can flash your bios with the byte sequence 'lolololol pwnd'". Personally, I'd rather have someone read my sudoers file than hose my BIOS, but hey... at least windows has cool games or something.

      --
      My other car is first.
    11. Re:How about pointing out... by freedom_india · · Score: 2, Insightful

      Are U propagating the myth that multi-platform means Windows 98, Windows ME, Windows 2000, Windows XP and Windows Vista* ?

      --
      "Doing what i can, with what i have." ~ Burt Gummer
    12. Re:How about pointing out... by LnxAddct · · Score: 5, Insightful

      So out of curiosity, I removed all (Updated) lines from the results,and all blatantly duplicate exploits, and also any non-linux exploits, just to see how they matched up. Keep in mind that I kept alot of the php, apache , and other exploits in the list but did not add them to windows despite that these also affect windows and should be included. The numbers I got were 784 to 672, Linux to Windows. Then, because in the windows list they strictly kept to vulnerabilities that only affected windows and not multiple platforms, I took out any vulnerabilties from the linux list that would 100% for certain be cross-platform and affect Windows as well. The list reduced to 669, which is right on par with Windows (keeping in mind that I left some exploits in the list because I was only say 80% or 90% sure and so I gave Windows the benefit of the doubt). Just out of curiosity, I then tookout any linux vulnerabilities that were specific to one vendor(i.e. Red Hat, Suse, Gentoo, Debian) for a number of reasons which I won't get into. This brought it down to 639. That last number doesn't really represent anything other than a curiosity of mine.

      I was originally going to have a disclaimer stating that these numbers are accurate probably to within +-30, but since they were so close, I don't think it's necessary. One observation I've noted is that the Linux vulnerabilities are spread over a far greater variety of applications. Another thing worth noting is that it looks like Windows can not easily be effectively secured as long as security updates are done as they are currently. Most linux distros (Red Hat/Fedora, Suse, Debian, Gentoo, etc.. off the top of my head) provide a central repository that will update everything on your system for you. This appears to be a much more optimal method of applying updates. If nothing else, these results show that not just core functionality, but also supporting functionalities must be kept up to date and are just as much of a security problem, if not more so. Linux distributions support such update methodolgies natively, Windows does not.

      It appears that Linux is the winner here no matter how you look at it, and we didn't even begin to look at severity or the time from disclosure to time patched (which isn't available using the information in the report, but my inclination is to say that open source wins hands down here, call me biased if you will). For the files that I referenced and modified to get these numbers, you can get the windows list here and the first linux list here (the one with 784 exploits, not 669). These lists are not 100% accurate as I'm sure the regexs I used missed some things, or were too greedy in other cases. I also did some manual pruning that wasnt appropriate to be done with regexs, which I'm sure wasn't 100% accurate either, but these lists are close.
      Regards,
      Steve

    13. Re:How about pointing out... by david_costanzo · · Score: 2, Interesting
      and more over, these were not just *nix vulnerabilities, they were *nix apps. If we included every security flaw in every program that runs on windows this year I feel that ths list might grow a bit......

      The list is supposed to include every security flaw in every program that runs on Windows. Check the Windows list; most of them are 3rd party apps and some are open source. Likewise, the UNIX/Linux list includes a lot of proprietary software. This study was examining which OS is more secure on the whole (apps and all), not if Microsoft writes more secure code than the Open Source community.

      For example, take a look at Adobe's contributions to both lists.

      From Windows:

      • Adobe Acrobat and Reader File Discovery
      • Adobe Acrobat and Reader File Discovery (Updated)
      • Adobe Acrobat Reader Invalid-ID-Handle-Error Remote Code Execution (Updated)
      • Adobe License Management Service Elevated Privilege Vulnerability
      • Adobe SVG Viewer Lets Remote Users Determine if Files Exist

      From UNIX/Linux:

      • Adobe Acrobat Reader mailListIsPdf() Buffer Overflow (Updated)
      • Adobe Acrobat Reader mailListIsPdf() Buffer Overflow (Updated)
      • Adobe Acrobat Reader UnixAppOpenFilePerform Buffer Overflow
      • Adobe Acrobat Reader UnixAppOpenFilePerform Buffer Overflow (Updated)
      • Adobe Reader / Acrobat Arbitrary Code Execution & Elevated Privileges
      • Adobe Reader For Unix Local File Disclosure
      • Adobe Version Cue for Mac OS X Elevated Privileges
      • Adobe Version Cue for Mac OS X Elevated Privileges (Updated)
    14. Re:How about pointing out... by Ohreally_factor · · Score: 2, Informative

      Not probably. The same vulnerabilities were counted multiple times.

      See this story over at Groklaw

      --
      It's not offtopic, dumbass. It's orthogonal.
    15. Re:How about pointing out... by Bert64 · · Score: 2, Insightful

      Well, a hole in a php app could exist on windows too.. Apache and PHP can easily be installed on windows. Infact there are many such vulnerabilities..
      There are also some, like the shell:// vuln that was attributed to firefox, but was actually a vulnerability in the core windows os and therefore wasn't exploitable through firefox on any other platform.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  15. Re:perfect place to discuss, though by aywwts4 · · Score: 2, Funny

    "so let the debate begin again over which OS is really more secure."

    How about we don't and just say we did, better yet, whichever side you agree with, it won the debate.

    --
    Web Developers: Celebrate to our roots! Animated Gifs and Tiled Backgrounds, dont let our history die!
  16. Do you realize just what you're saying? by hahafaha · · Score: 2, Insightful

    The title: Linux/Unix Tops Charts for Vulnerabilities in 2005

    This is beyond any doubt, very very true. But before you call me a Microsoft Shill (I'm not, I use Debian myself), allow me to explain:

    If one goes to www.linux.org, and searches for all GNU/Linux distros without a filter, they will see that there are 370 distributions. If that includes unmaintained ones, that number grows to 417. And that does not include all of the other Unixes, such as the BSD group, and, like the article pointed out, Mac OSX.

    Now compare that to the Microsoft Windows operating system. Let's see, Windows 98 (I doubt people use anything worse than this), ME, 2000, XP, and even Vista. 5 operating systems. 370 / 5 = 74. Now the article claims that there were 3 times as many vulnerabilities. 74/3 = 24 and 2/3.

    Unix/Linux is approximately 25 times better than Windows!

  17. only 3x ? by DaveCar · · Score: 2, Insightful

    Well, the "windows" ones are "Windows Operating Systems"

    And the "linux" and "osx" ones are "Unix/ Linux Operating Systems"

    Seeing as "windows" ones are Windows and "linux" and "osx" are Linus, OS X, Solaris, IRIX, AIX, HPUX, Tru64, *BSD, SCO, etc., etc., I think 3x is not too bad as there are more than 3x the number of distinct operating systems.

    That's without even looking at what might be classified as "application" versus "os" vulnerabilities in each category.

  18. Regardless of the validity of the article... by daVinci1980 · · Score: 3, Insightful

    It is worth discussing OS security in terms of exploitable holes found. And before the detractors start coming out in droves saying "the real question is how many days a vulnerability remains unpatched," that's not the real question. That's a question, and it's certainly an important one. But it's not the only important criteria in determining the quality of an OS.

    Even if a vulnerability is reported and then fixed quickly, the fact remains that it could've been used for dozens or hundreds (or more) exploits *before* it was reported.

    It's not just a matter of "see, look how quickly we can bail water out of the boat." There's also the question of how many holes were in the hull to begin with.

    I'm not saying that any particular platform is put together better than any other, just that it is a topic worth discussing.

    --
    I currently have no clever signature witicism to add here.
  19. Dear Slashdot, by hellomynameisclinton · · Score: 5, Funny
    Dear Slashdot,

    I'm offended by the latest comparison of
    Linux
    and
    Windows
    . The linked article offers no measurable insight, and is exactly the kind of flamebait that bores the /. community. It goes without saying that I did not read the article, but I know enough about
    operating systems
    that it is incorrect, and insight-free.

    Please change your editorial practices to fit my tastes better.

    ComplaintGen (R) - 2006
    1. Re:Dear Slashdot, by Linker3000 · · Score: 5, Funny

      Slashdot EeziPost (TM) MK 1.1.01

      #NB: For obvious reasons, the first option is ENABLED by default - remember to turn off if you are NOT responding to a dupe

      [ ] Another: [ ] Dupe [ ] Slashvertisment [X ] WTF [ ] $editor is a dork

      [ ] Frist psot [ ] $link_to_GNAA [ ] $link_to_goatse [ ] $random_drivel

      [ ] I Haven't RTFA, but... $random_self_opinionated_comment

      [ ] [$Slashdot_reader] writes, "[$pundit] wrote an article about [$Technology_we're_not_currently_fond_of], based on conjecture and personal opinion. Does this mean that [$Technology_flavor_of_the_month] is taking over?

      [ ] Slashdotted already!. I bet their server runs on $topic_item too!

      [ ] I am not qualified to respond to this article, but I will give you my insight anyway..

      [ ] Here's a plug for my blog / Web site disguised as an insightful comment (I need the ad revenue)

      [ ] Next they'll be patenting 'A method of replying to a Slashdot posts using a form containing pre-defined response options'

      [X] Mod Parent [X] up [ ] Down

      [ ] Fsck: [ ] Sony [ ] SCO [ ] Micro$oft [ ] DMCA [ ] DRM [ ] MPAA [ ] RIAA [ ] Google [ ] Bush [ ] You all

      [ ] I for one welcome our new $topic_item overlords

      [ ] Imagine a beowulf cluster of those

      [ ] In Soviet Russia, $topic_item owns you!

      [ ] Meh!

      [ ] You must be new here!

      [ ] Netcraft confirms $topic_item is: [ ] dead [ ] dying

      [ ] But have the inventors thought of what will happen if $random_amateur_insight

      [ ] You insensitive clod

      [ ] Torrent, anyone?

      [ ] Here's a link to a patch: $random_linux_distro_url

      [ ] "Yeah, but does it run Linux?"; if($summary has 'linux') add " Oh, wait..."

      [ ] Profit!!

      [ ] Tinfoil hat at the ready

      [ ] Still no cure for cancer

      [X] "()*%£^" No Carrier

      --
      AT&ROFLMAO
  20. Too Big of a Bucket by Crispin+Cowan · · Score: 2, Insightful
    The reason the numbers are so different is that they are apples and grapes: different sized units. Lumping all of Linux and UNIX together into a single category distorts the data. The fact that Solaris or AIX had some defect does not affect Linux and *BSD systems. Putting all their union set of vulnerabilities into a single bucket makes the UNIX/Linux crowd look much more vulnerable than it is. FUD FUD FUD.

    Another issue is that most Linux distro's ship a LOT of application code, like 2000 to 6000 packages, which is waaaay more than Microsoft ships with Windows. That there is an "OS" vulnerability for some rarely used application in a large Linux distro is just not comparable to the smaller set of code that Microsoft is willing to take responsibility for.

    It is just irresponsible for CERT to be publishing distored numbers like this.

    Crispin

  21. Let the flamewar begin by TheFlyingGoat · · Score: 2, Insightful

    Volatile is an understatement.

    Anyway, I've used a number of different operating systems and I've realized something. Computer security isn't so much the operating system you select, it's how diligent you are in keeping it secure. If you keep the system patched, behind a decent firewall, are careful with the software you run, and don't use the root/Administrator account for normal usage, you'll probably not have any issues with your computer. Granted, there are plenty of examples otherwise, but I'm referring to the standard user or sysadmin.

    The problem comes in for users that don't understand that they need to keep their system protected more than it is out of the box. Some linux distros and Windows get it right by having automatic updates (if you need to disable these, you can easily enough).

    Overall, there ARE good things and bad things about each operating system, but not much matters if the user isn't going to take some type of responsibility to keep their own system updated and protected.

    --
    You have enemies? Good. That means you've stood up for something, sometime in your life. --Winston Churchill
  22. Groklaw commentsx by Phragmen-Lindelof · · Score: 2, Informative

    Groklaw has comments about this like:
    Second, the Unix/Linux list duplicates items, counting a vulnerability more than once in the list. For an example, note that it lists Eric Raymond Fetchmail POP3 Client Buffer Overflow (Updated). However, the same vulnerability is listed, under the same title, four times. That's because it was reported in the week of August 10-15, again in the week of August 17-23, in September 6-13, and the week of November 9-16. Worse, for any comparison purposes, the same vulnerability is also reported as Fetchmail POP3 Client Buffer Overflow, so in reality one vulnerability is listed 5 times, making the total of 2328 meaningless unless you carefully comb through it to weed out duplications.
    Kind of makes a numerical count of reported security problems pointless. (BEGIN SARCASM) Of course, the Linux/Unix security holes are much more serious than are Windows security holes because automated worms. viruses, etc. attack Linux/Unix machines but not Windows computers.(END SARCASM)

  23. Vulnerabilities are only vulnerabilities IF... by wyattburp · · Score: 2, Insightful

    This is all out of context unless you look at the impact of the vulnerability, and how it is exploited. I didn't RTFA, admittidly, but I do know that the main reason for the exploit of vulnerabilities (both technology speaking, as well as the handling of these topics by the media) is largely because of the volume of Windows users in the world.

    These articles only make the majority of the public even dumber.

    It makes me think of the line from Billy Madison where the teacher proclaims "...At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it..."

  24. Re:perfect place to discuss, though by tomhudson · · Score: 4, Insightful

    Since this is a dupe debate (it happens ALL the time) why not just link to the previous list of comments? I'm not even going to read TFA, because these useless debates have gotten to be a waste of time. There's no winning this debate - we're all losers for having editors who think that this is "news".

  25. "OS Vulnerability" vs "Application Vulnerability" by javaxman · · Score: 4, Interesting
    There are more than one problem here, but something which must not be ignored is that a large number of the listed 'vulnerabilities' are very application-specific.

    Want one example? The CM Cyrus IMAP server sure as heck isn't installed on my Mac OS X system, and I doubt I'd ever install it. I don't think I'd install it on my Linux box, either. If I did install it, and there was a bug in it, I sure as hell wouldn't consider that bug an "OS" problem, would you ?

    And I'd be willing to make the same distinction for Microsoft, as well, at least so long as the application error isn't in a default-installed DLL or in an always-installed application, like... oh, Internet Explorer, for example. I'm not so sure I should fault Windows because the Eternal Lines web server has some sort of issue. There's the OS, then there are the apps that run on top of the OS.

    So really, the counting and analysis are so broken that it's hard to even discuss. Call me back when individual distros and specific OS kernel builds are broken out into separate counts. Call me back when non-default-installed or at least not-commonly-used applications are broken out ( i.e. I'll give you web servers and browsers normally used with any platform as part of the OS ), but I don't think Linux in general is less secure because Joe's Custom Server has a bug in it. I'd like to see some *useful* summary of this information, please...

  26. Here's a quick answer: by khasim · · Score: 5, Interesting
    TFA says that there were 2,328 reported vulnerabilities for *nix.

    I counted the lines and there are 2,329 lines.

    Here's an example of 10 of them:
    # BZip2 File Permission Modification
    # BZip2 File Permission Modification (Updated)
    # BZip2 File Permission Modification (Updated)
    # BZip2 File Permission Modification (Updated)
    # BZip2 File Permission Modification (Updated)
    # BZip2 File Permission Modification (Updated)
    # BZip2 File Permission Modification (Updated)
    # BZip2 File Permission Modification (Updated)
    # BZip2 File Permission Modification (Updated)
    # BZip2 File Permission Modification (Updated)

    Yep. BZip2 is listed 10 times, but the reference to each of them reads the same:
    A vulnerability has been reported when an archive is extracted into a world or group writeable directory, which could let a malicious user modify file permissions of target files.


    And then they list 10 different distributions. Hmmmmm ..... it looks like the old "multiple reporting" problem.

    So, one problem in BZip2 == 10 counts of "problems".
    1. Re:Here's a quick answer: by Lehk228 · · Score: 2, Funny

      yea, we all know what "use palm OS" is code for, keep your hairy palms away from me

      --
      Snowden and Manning are heroes.
    2. Re:Here's a quick answer: by OdieWan · · Score: 5, Interesting

      Removing the duplicate lines is enlightening;
      cat usoft.txt| sed -e 's/(U|updated)//g' | sort | uniq | wc
          747 lines
      cat unix.txt| sed -e 's/ *(Updated) *//g' | sort | uniq | wc
          1050 lines

      That brings them almost in line with each other. Of course, we could do a half-assed job of cutting things down to just the OS to remove concerns about all the bundled apps;

      cat usoft.txt| grep Microsoft | sed -e 's/(U|updated)//g' | sort | uniq | wc
          160 lines
      cat unix.txt| egrep '((K|k)ernel)|(GNU)|(XFree86)' | sed -e 's/ *(Updated) *//g' | sort | uniq | wc # GNU/Linux, not Linux!
          167 lines

      Of course, any of this would be far too much work for the author of the article.

    3. Re:Here's a quick answer: by aaronl · · Score: 2, Insightful

      The sed lines are removing the "updated" string from each processed line. Sort is grouping lines, uniq is removing all duplicated entries.

      sed -e(expression) 's(search)/(U|updated)(search regex)/(empty replacement text)/g(global)'

      So:
        1
        2
        1 (Updated)
        1 (updated)
        2 (Updated)

      Becomes: (through sed)
        1
        2
        1
        1
        2

      Becomes: (through sort)
        1
        1
        1
        2
        2

      Would drop to simply: (through uniq)
        1
        2

      And then "wc" counts the lines.

      In this case, the GP compressed it to 747 unique Microsoft flaws, and 1050 unique unix flaws.

      And yes, learn regex! It is extremely useful, and can help manipulate massive data sets easily and quickly. "man 7 regex" is a good place to start. :) There are much better places to start, mind you.

  27. TFA sums it up: by Savage-Rabbit · · Score: 4, Insightful

    The end-of-year vulnerability score should be taken with a grain of salt, however, since US-CERT doesn't filter out updates (so one actual vulnerability can be counted numerous times) nor does it break out individual vulnerabilities from warnings that cover multiple bugs (as in the many Mac OS X vulnerability listings).

    In effect: This information is completely useless for comparing operating systems.

    --
    Only to idiots, are orders laws.
    -- Henning von Tresckow
  28. I completely disagree with the article. by u-235-sentinel · · Score: 2, Insightful

    so let the debate begin again over which OS is really more secure.

    I hear this junk all the time and can't believe people can say an OS is secure / insecure by the "applications" running on it. How is "Adobe Acrobat Reader" a reflection of how "insecure" Linux is? Or a problem with "Apache mod_install"? These are all applications which run on top of Linux. They are NOT the Linux OS by any means. The same goes for Windows with "Adobe Acrobat Reader" and "IBM Websphere". I would argue this is a garbage comparison.

    Now compare what IS inside the OS. Windows cannot function without IE (according to Bill Gates). It's been incorporated deeply into the OS. Security problems with IE would qualify as a problem with the OS (for example). If it's something part of the OS then I would buy it as a security problem. Linux issues IMO would include problems such as say iptables, Linux Kernel Race Condition / Buffer Overflow and maybe Gnome/KDE (to name a few)

    I understand I may be just a little picky about this but I think I've demonstrated my argument.

    --
    Has Comcast disconnected your Internet account? Same here. You can read about it at http://comcastissue.blogspot.com
  29. 2,328 bugs found is 2,328 bugs fixed. by Stuupid · · Score: 4, Funny

    2,328 is a whole lot more than 812. that means that *nix et al are 1,516 fixes ahead of the competition.

  30. BeanBunny is a known troll by Anonymous Coward · · Score: 5, Insightful

    and submitting something like this (just as the parent and GP have pointed out), that lumps every *NIX OS vs. MS Windows is perhaps the dumbest thing I've ever seen on /.. I wish I could mod submissions.

    1. Re:BeanBunny is a known troll by floamy · · Score: 2, Funny

      An account only lets you moderate comments. He wishes he could moderate submissions. What type of psychoactive are you on?

    2. Re:BeanBunny is a known troll by MECC · · Score: 5, Insightful

      Actually, it wasen't BeanBunny that lumped the various 'Nixes and 'Nix-like OSes into one catageory - it was CERT. Also, the CERT list include all vulnerabilities for all software running on an OS, not just the os themselves. Also , its only a list - no mention of how severe a given vulnerability is.

      To really get a picture of how the OSes themselves stack up in comparison to one another with respect to vulnerabilities, try Secunia. They list vulnerabilities, and how severe a vulneraiblity is, and why a given vulnerability is a problem, along with other interesting and relavent info about vulnerabilities.

      --
      "We are all geniuses when we dream"
      - E.M. Cioran
  31. Important points not mentioned by necro2607 · · Score: 4, Insightful

    Points not mentioned :

    -amount of risk caused by vulnerability
    -percentage of high-risk vulnerabilities per OS
    -time taken to patch vulnerability
    -whether the vulnerability is in some tiny obscure piece of shareware or in a VERY common software (such as MSIE) ... etc. etc.

    Statistics aren't so useful with such lack of completeness.

    Of course that page isn't there to be a useful guide for statistics on vulernabilities, but the Slashdot article seems to be portraying it as such...

  32. Ignorant Users Though by WlfRecon · · Score: 2, Interesting

    The thing is, I see most people here actually analyzing the data and seeing the flaws within it. But many many computer users will simply see the headlines and start telling everyone that there are these things called "Linux" and "Mac" that are really insecure, so everyone should use Windows.

    --
    Semper Fi
  33. windows and intelligent design by 3seas · · Score: 2, Insightful

    The only intelligence there is in regards to windows is that of marketing... market it no matter what condition it is in. If "Intelligent Design" was more popular you can be sure MS would market Windows in a manner to ride off that, as they do everything else they can. I mean Hey, they got the singularity OS....(rolls eyes)

    I think everyone knows how out of context the article is, which only shows the deceiptful intent of those responsible for it being written.

    Taking things out of context is a known action of those having intent to deceive.

    Now if there were laws against such that applied to marketing.... We'd all have better things in life, cept for the deceptive.

    But for those of us who do know to see past the BS... we are better off, depending on how deep the BS goes, and sometimes its gets rather deep.

  34. Worse than that by Lifewish · · Score: 2, Informative

    If I recall correctly, they're actually double-counting some vulnerabilities in common software - once for Linux, once for OS/X, once for Sun Solaris etc (I think that was right - can anyone confirm?). None of this was malicious - this survey was never intended to be rigorous and the people doing the counting made that quite clear. However, it does mean that any attempts to judge the relative merits of the various operating systems are somewhat fruitless.

    --
    For the love of God, please learn to spell "ridiculous"!!!
  35. lies, damn lies, and statistics... by smash · · Score: 2, Insightful
    OK, lets consider:

    1. Your typical linux distribution includes more applications than microsoft even produce
    2. choosing not to install, or uninstall specific components of a linux distribution is trivial. Try removing IE from Windows XP, without having to put your faith in a third party to help you hack the OS to do it. Then call microsoft for support :D
    3. "linux" encompasses more than 1 distribution

    Anyone with half a clue and experience with both OSes in a production environment already knows the truth, but there's some points for those who actually believe some of the shit that seems to be deemed newsworthy...

    smash.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  36. More than half of these are dupes or updates by Anonymous Coward · · Score: 2, Informative

    I copied the list to a file ran 'uniq' and 'grep -v "(Updated)' on it to remove any duplicates and rows contaning the string 'Updated'.

    Only turned up 813 lines.

    This article in a TLA : WTF ?..

  37. Puh-lease by MattW · · Score: 4, Insightful

    Go compare "Linux Kernel" vulnerabilities (9 unique) vs "Microsoft Windows" vulnerabilities (46 unique). Even that isn't apples to apples, but it's a lot more indicative than the random counts of vulnerabilities for every piece of software shipped with an OS.

  38. W[e] M[ay] F[ail] by ntropia · · Score: 2, Funny

    Funny!
    Windows shows less bugs than Linux/Unix! I was always shure that Micro$osft is the best.
    No Office suite exploits... It should be secure, now!
    And, however, even kids knows that "A known bug is a dead bug"!
    (same kids knows that "Bugs enter from open Windows")
    What? WMF? Still unpatched since 3 months? But is a bug related to a feature coming from 1990, it's not a real bug...
    What? Is a *deadly* bug?
    But a company that depict his logo on my keyboard can't be wrong!

  39. Good idea, bad implementation by egarland · · Score: 3, Insightful

    The idea of a security score card is good but the way they did it is meaningless. The ranking should be more like:

    Number of bugs +
    Number of bugs with known exploits x 5 +
    Number of bugs with known exploits x the number of days the exploit was in the wild before the bug was patched.

    Then multiply the whole thing by an risk factor (1-5) based on how much harm it can do.

    No lumping multiple OSs. Each one should get it's own card. Lumping applications bundled with the OS is reasonable but skews things too. For an accurate comparison, only bugs in features common to all platforms and bugs in non-optional components should be counted.

    The way the current ranking they use works you could have 50 non-exploitable, local user only, file permission modifying bugs in 100 different Lunix distributions and it would count as 5,000 bugs. Similarly you could have one remote attack that completely takes over a Windows box with known exploits which remained unpatched for 100 days and it would count as 1 bug. The score would be 5,000 to 1 in favor of Windows which is about opposite from what it should be in this example. These are completely meaningless numbers.

    I don't know how the OSs would stack up given an accurate reporting but I would be interested to see.

    --
    set softtabstop=4 shiftwidth=4 expandtab nocp worlddomination
  40. Re:Suuuuure by dsci · · Score: 4, Informative

    What percentage of discovered bugs do you think are actually found by looking at the source code of a program?

    All of them?

    I know your point: that the INITIAL discovery and exploit is not typically found by looking at the code. But to fix vulnerable code, one must FIND and edit it. The point is, once an exploit is discovered, there are many people who can locate the faulty code and fix it fast.

    Open Source is a good thing. Really, what is the down side of source code availability?

    --
    Computational Chemistry products and services.
  41. Rubbish by Brandybuck · · Score: 2, Informative

    Utter rubbish! This is comparing one operating system with two varieties to a dozen different Unix and Unix-like operating systems with hundreds of variants, distributions and versions.

    How about comparing just ONE operating system to ONE other operating system? Like Windows XP to Solaris/SPARC? Or Windows Server to FreeBSD 5.x branch?

    --
    Don't blame me, I didn't vote for either of them!
  42. Even worse, the way the stats are grouped!!!! by Fallen+Kell · · Score: 2, Informative
    At first glance it looks like the groupings have MS as a better OS in terms of CERT warnings, but not even that, look at how the bins are made which group the numbers together.

    Basically UNIX (BSD, Solaris, AIX, IRIX, SCO, OS X), and ALL LINUX distributions are counts as ONE (1) bin, against MS Windows!!! So, have basically EVERY popular mainstream operating system other then Windows in one bin and windows in another, and you are trying to toute THAT as a stat that Windows has less flaws then Unix/Linux? Sure, it does when you count ALL VERSIONS OF UNIX AND LINUX TOGETHER AND ADD UP ALL THE VULNERBILITIES FOUND IN ALL THE DIFFERENT VERSIONS!!!!!

    THEN there is the fact that different CERT warnings appear multiple times! For instance, Eric Raymond Fetchmail POP3 Client Buffer Overflow (Updated) is counted at least 4 times under the SAME NAME, and at least 1 more time under a different name, but it is still the same vulnerbility!!!

    See http://www.groklaw.net/article.php?story=200512311 42317870 for more details.

    --
    We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
  43. Meaningless numbers by laird · · Score: 2, Interesting

    These aggregate numbers are meaningless. That being said, US-CERT made pretty clear that this was simply a list of reported vulnerabilities, not any sort of analysis, so I blame the news sites with taking the meaningless numbers and trying to create a news story that will get Windows and Linux/UNIX/MacOS X fans all excited to read and post (and generate ad revenue).

    Why do I say that the aggregate numbers are meaningless?
    1) They count "updates" to vulnerability reports as vulnerabilities, so there are many vulnerabilities that appear to be counted 5-10 times in the "UNIX" list, and 2 times in the "Windows" list. My guess is that these "updates" are individual OS reports, meaning that a single vulnerability in a cross-platform application would be reported as 2 Windows vulnerabilities and 10 UNIX vulnerabilities. CERT should break out each OS into its own counts in order to correct for this. Eliminating duplicate reports isn't good enough, because there are many OS-specific reports, and it doesn't make much sense to count vulnerabilities specific to Solaris AND Mac OS X AND Linux AND HPUX etc., in a single number, since you run only one OS as a time. :-)
    2) They count reports of multiple vulnerabilities as a single vulnerability, which means that OS's that release fewer updates, each of which patch multiple vulnerabilities (e.g. Apple, Microsoft) as having far fewer vulnerabilities than OS's that release specific patches for each vulnerability. Strangely, this punishes OS vendors that rapidly address and release patches for vulnerabilities, and reports vendors that are less responsive. CERT should count a single announcement that covers multiple vulnerabilities as if each vulnerability were reported individually.
    3) They include third-party application vulnerabilities in the counts, and the number of those reports dwarfs the number of actual OS vulnerabilities (90-95% of the vulnerabilities listed aren't in the OS's). CERT should separate bugs in the OS's from optional third-party application bugs. Many of the vulnerabilities are in extremely obscure applications, and while uses of those applications might want to know about these issues, it's hardly a reflection on the OS' security if there's a 'Wojtek Kaniewski EKG Insecure Temporary File Creation & SQL Injection' in some project's "contrib" directory, which is hardly comparable to 'Sun Solaris ARP Handling Remote Denial of Service' or 'Microsoft DirectX DirectShow Arbitrary Code Execution'.
    4) Their OS coverage is quite spotty. For example, if an application runs on all OS's (e.g. Mozilla, bzip) and has a vulnerability that applies to all OS's, sometimes they're reported only for Windows, sometimes only for UNIX, sometimes for both, sometimes with many repetitions and sometimes only once. While this would require CERT to do some analysis (i.e. actually read the reports), they should consistently recognize cross-OS issues and remove them from the OS-specific lists and report them in the multiple operating system list.

    Since each of these issues appears to introduce error rates that are an order of magnitude larger than the useful data, there's nothing meaningful data left.

    Of course, people have pointed these problems out about these CERT reports for many years. Still, since we have these same pointless discussions every year, CERT should make some basic changes to make these reports somewhat meaningful. Their previous years' list (http://www.us-cert.gov/cas/bulletins/SB2004.html) were more useful, because they at least made it clear which issues were high risk, and which application or OS each vulnerability was associated with, and they avoided the misleading totals. Let's hope that next year they at least go back to the 2004 report format, even if they don't bother to do any meaningful analysis.

  44. Re:Suuuuure by toadlife · · Score: 3, Insightful

    I never said open source was a bad thing, or there was a downside. Just that that particular 'benefit' is overrated. Firefox bugs are certainly fixed faster than IE bugs - but according to my logs half of firefox users who hit my website still run vulnerable versions.

    --
    I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  45. Vulnerability vs Exploit by yeOldeSkeptic · · Score: 3, Informative

    There is a difference between a vulnerability and an exploit. A vulnerability is just a potential weakness, a chink in the armor so to speak, but potential weaknesses cannot be taken advantage of unless it is exploited. It is thus the number of exploits that is the primary consideration when speaking of security.

    Of course, Linux will have a large number of visible vulnerabilities! It is open source and anybody with two eyes and a passing knowledge of C should be able to find vulnerabilities almost everywhere. However, are those vulnerabilities actually exploitable? In most cases, Linux security alerts consist entirely of possible vulnerabilities and in most cases also, those vulnerabilities are quickly patched up and repaired; well before any practical exploits are written for it.

    The case is not the same with Microsoft Windows. Because Windows is closed-source, the only way to demonstrate a vulnerability in Windows is to actually write an exploit for it! Thus, whenever a vulnerability has been discovered for windows, you can bet your Momma's last penny that there is a very good chance of the existence of a working exploit for it.

    How many vulnerabilities are there in Windows we do not know of because we cannot examine the source? Judging from the number of exploits (written by people without access to Windows source code, by the way) we can infer with good accuracy that the total number of vulnerabilities in windows should be several times that of the number of exploits. I am too lazy to make a count but perhaps someone with the inclination can create a matrix showing Vulnerabilities vs exploit vis a vis Windows vs Linux. If we assume that the ratio of exploits to vulnerabilities is the same for both operating systems, what would be the estimate of the number of vulnerabilities in windows? If we further include the fact that Linux is open source while Windows is not, what would be the estimated number of exploits in Windows?

    That would make an interesting study.

    It is Linux's open-source nature that gives it the disadvantage when a simple-minded count of the security alerts for Windows versus the number of security alerts for Linux is made. But keep in mind that almost all security alerts for windows are not of vulnerabilities but of practical, demonstrably working, and potentially already widespread exploits. Most security alerts for Linux are of vulnerabilities.

    In any discussion of security between Linux and Windows, the crucial distinction between vulnerability and exploit should be clearly enunciated.

  46. Re:Suuuuure by stevey · · Score: 4, Informative

    All the bugs I find and report which result in Advisories are as a result of source code auditing.

    It looks like I made the CERT list a couple of times, e.g. uw-imapproxy.

    But these bugs are trivial things in applications which are either "extra", or not typically installed.

    Fixing bugs in programs is important, but having a list of 500 simple buffer overflows in rarely used games (for example) on Linux says nothing about the relative security of Linux vs. Windows.

    The worlds are too different, comparing every application included in Debian, say, against Windows would only make sense if you installed every single shareware/freeware/optional piece of software on the windows machine - and that clearly isn't a real world scenario.

  47. Re:So what's new? by Ohreally_factor · · Score: 2, Funny

    That article is from last year.

    =)

    --
    It's not offtopic, dumbass. It's orthogonal.
  48. Re:Suuuuure by shmlco · · Score: 3, Funny
    "..but having a list of 500 simple buffer overflows in rarely used games.."

    You should look at the list. http://www.us-cert.gov/cas/bulletins/SB2005.html Hardly any are "rarely used games", unless "Multiple Vendors Linux Kernel Asynchronous Input/Output Local Denial Of Service" is the latest FPS...

    --
    Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
  49. Re:Suuuuure by Bert64 · · Score: 2, Interesting

    It's easy to find a crash-scenario without the sourcecode, but to actually determine if the vulnerability is exploitable or not takes a lot longer, and is much easier to find in the sourcecode.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  50. Re:Mod Parent Up by Bert64 · · Score: 2

    Well there's the diversity among unixes..
    A single worm is unlikely to affect such a large proportion of users, since they will be spread out among different unixes and different distributions of linux etc..
    Windows on the other hand, has a few distinct versions which are easily identifiable and easy to target in exploits.. The dcom worms for instance, differentiated between XP and 2000 and used appropriate parameters.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  51. OFF TOPIC -- Good suggestion here, CowboyNeal! by Dystopian+Rebel · · Score: 4, Interesting
    I wish I could mod submissions.


    Why not make this one of a subscriber's privileges?
    --
    Rich And Stupid is not so bad as Working For Rich And Stupid.
    1. Re:OFF TOPIC -- Good suggestion here, CowboyNeal! by DrMorris · · Score: 4, Interesting

      What about modding the editors? I would especially like a button [decrease karma for posting a dupe... again] :-)

  52. Re:Suuuuure by Pieroxy · · Score: 3, Funny

    what is the down side of source code availability?

    The inability to maintain a monopoly by using scare tactics?