Slashdot Mirror


Firefox Greasemonkey Extension Security Problem

Mr2001 writes "A recent thread on the Greasemonkey mailing list suggests that the popular Firefox extension is fatally insecure. It seems rogue pages can read any file from your disk and send it to any site, using an XmlHttpRequest. Time to uninstall GM?"

91 of 443 comments (clear)

  1. It's about time by rockytriton · · Score: 4, Funny

    It's about time people start writing some exploits for firefox!

    http://www.dreamsyssoft.com

    1. Re:It's about time by Mantus · · Score: 4, Insightful

      I'm not sure why this post got modded as flamebait, It's somthing that will happen. As FF gets more popular more holes will be found, some won't get reported right away. MS aren't the only people that don't write 100% secure code.

    2. Re:It's about time by Anonymous Coward · · Score: 2, Informative

      but this isn't a security hole in FF. it's a security hole in an extension. dontcha understand the difference, wee man? :rolleyes:

    3. Re:It's about time by ad0gg · · Score: 4, Informative
      Umm IIS6 has less exploits and no unpatched vunerabilities compared to Apache 2.0.x which still has unpatched vunerabilities.

      IIS 6 Exploits
      Apache 2.0x.

      Please do some basic research before making comments on security.

      --

      Have you ever been to a turkish prison?

    4. Re:It's about time by jerw134 · · Score: 4, Informative

      Surprisingly enough, IIS5, still in wide use, has unpatched vulnerabilities.

      OK, stop with the pure FUD. Using the Secunia link you provided, it shows that IIS5 has one unpatched vulnerability, which is rated Not Critical, which is the lowest rating possible. Not only are the unpatched flaws in Apache more serious, there are also more of them! Please, stop with the BS.

    5. Re:It's about time by DA-MAN · · Score: 2, Interesting

      Umm IIS6 has less exploits and no unpatched vunerabilities compared to Apache 2.0.x which still has unpatched vunerabilities.

      Have you looked at the apache security vulnerabilities? There was only one in 2005, and here is the link to the cve:

      http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN- 2004-1387

      It's not even about apache, it's about a third party apache-utils. That package isn't even part of my distro. i have no such script called check_forensics.

      The only other unpatched issue with apache is this one:

      http://secunia.com/advisories/11176/

      Which is rated as non-critical. And it says it's confirmed for 2.0.46 and lower. The latest version is 2.0.54.

      Regardless IIS6 & Apache have both been really good. A lot of IIS's reputation comes from IIS5, and let's face it, it is really well deserved. IIS5 is horribly unsecure without first running the lockdown tool, which not all Win Admin's do!

      --
      Can I get an eye poke?
      Dog House Forum
  2. gauntlet by Anonymous Coward · · Score: 4, Funny
    Rogue pages???

    Quick, lets band together with a magician and a warrior and stomp those bow&arrow shootin mofos before they take over the internet!

    1. Re:gauntlet by adrianbaugh · · Score: 4, Funny

      You have been killed by a Firefox on Level 8 with 5439 Gold. RIP.

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    2. Re:gauntlet by wuie · · Score: 5, Funny

      Yellow wizard needs patch badly.

    3. Re:gauntlet by TheScottishGuy · · Score: 5, Funny

      Blue browser is about to die.

  3. GreaseMonkey Problem by RagingChipmunk · · Score: 2, Funny

    Damn Microsoft! No doubt this can be traced to a Bill Gates directed consipracy against rebel browsers.

    --
    The only PT Boat Journal on the web: http://www.PT171.org
    1. Re:GreaseMonkey Problem by wheany · · Score: 4, Funny

      Okay, how's this: Since Microsoft Internet Explorer has a dominant market share, people make pages that work on IE. Some of the pages do not work on Firefox since they use some functionality found only in IE. Greasemonkey can be used to alter some of those pages so that they work on Firefox again.

      It's Microsoft's fault that people have to install insecure extensions to make web work like it should have worked in the first place.

    2. Re:GreaseMonkey Problem by PHP+Addict · · Score: 2

      "You may be correct, but that's not what matters here."

      Only as long as assholes like you keep spreading that mindset.

      --
      Laziness, check. Impatience, check. Hubris, double check!
  4. 1000 greasemonkies on a thousand keyboards... by ScentCone · · Score: 2, Funny

    are going to produce some vulnerabilities along with the gee-whiz plugins of the moment. That's pretty spectacular, though.

    --
    Don't disappoint your bird dog. Go to the range.
  5. More Ammo by GuitarNeophyte · · Score: 5, Insightful

    Just more ammo for the mega-powers to say, "See, when it becomes mainstream, it becomes more insecure. Come back to windows."

    Marvelous.

    Luke
    ----
    Be smart. Teach others. ChristianNerds.com

    1. Re:More Ammo by ssj_195 · · Score: 4, Insightful

      If they do (as they doubtless will), you can simply say that this is an optional extension used by a minority of Firefox users (and since not even Firefox is fully "mainstream", this puts it about as far from the mainstream as you can get :P), and there are currently no exploits in the wild. You can also add that it was found by a white-hat, and so is a validation of the "many-eyes" theory, if you want. Spin works both ways ;)

    2. Re:More Ammo by FidelCatsro · · Score: 5, Funny

      They can say "Come back to windows , no need for third party extensions for these types of flaws .They are built into MSIE/windows , It just works"

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    3. Re:More Ammo by arrow · · Score: 4, Insightful

      The diffrence is your spin will never be heard by the media.

      --
      symetrix. We are building a religion, a limited edition.
    4. Re:More Ammo by Phisbut · · Score: 4, Insightful
      I'd hardly call Greasemonkey "mainstream" :o)

      Plus, the solution "uninstall it until we fix it" is pretty decent when it comes to security. Think we'll ever hear "Uninstall IE until we fix it" anytime soon? :o)

      --
      After 3 days without programming, life becomes meaningless
      - The Tao of Programming
  6. Why Uninstall? by SenFo · · Score: 5, Informative

    "Time to uninstall GM?"

    Why not just do what the article says and "Install Greasemonkey 0.3.5"

    1. Re:Why Uninstall? by DrEldarion · · Score: 4, Insightful

      See, you're making the (frequently-made) mistake of assuming that people actually read anything but the headline of the articles they're referencing.

    2. Re:Why Uninstall? by phasm42 · · Score: 4, Informative
      Because:
      Greasemonkey 0.3.5 is a "neutered" version of Greasemonkey, lacking any of the GM* APIs which make Greasemonkey scripts more powerful than regular HTML. This means that scripts which depend on GM* APIs will fail with Greasemonkey 0.3.5.
      --
      "No one likes working in a hamster wheel, and your shop smells of cedar shavings from here." - TaleSpinner
    3. Re:Why Uninstall? by psycho_tinman · · Score: 2, Informative

      Well, this is the recommended course of action. However, Greasemonkey 0.3.5 is crippled. It does not contain the special GM_ functions so the majority of scripts will break.

      Anything that uses GM_XMLHttpRequest, GM_setValue or GM_getValue or GM_Log will not function. It was the developers attempt to make sure that no remote exploits popped up while they were working on the best possible fix.

      So, no. Don't install the update and expect things to function normally, they will not.

    4. Re:Why Uninstall? by tgd · · Score: 2, Insightful

      I bet you a dollar those scripts won't work if you uninstall GreaseMonkey, too.

    5. Re:Why Uninstall? by CdBee · · Score: 3, Interesting

      Just install NoScript and you're sorted. It will stop any script - Greasemonkey or otherwise - running on any site except those you whitelist. I'm sure most of us only use scripts on sites we trust anyway

      --
      I have been a user for about 10 years. This ends Feb 2014. The site's been ruined. I'm off. Dice, FU
    6. Re:Why Uninstall? by Col.+Bloodnok · · Score: 2, Informative

      Well, 'Slashdot Recolor' and 'Butler' work fine under 0.3.5.

      That's all I need.

    7. Re:Why Uninstall? by jdavidb · · Score: 4, Interesting

      I thought that GM was a way for me, the web user, to impose some scripted changes onto pages. I didn't realize it was used by site-designers to do anything HTML (+JavaScript, etc.) didn't allow.

      I don't want to give site-designers any more power, so if that's prevented by neutering GM, I'm fine with that.

    8. Re:Why Uninstall? by Anonymous Coward · · Score: 3, Informative

      The idea is that the scripts which you let loose on the page can use the GM API to do things which are beyond (unsigned) web scripting, like reading a preferences file. These capabilities are only meant to be used by GM scripts. The problem is that scripts don't work on the page "from the outside". They are injected into the page. The GM API can't properly tell a webscript from a GM script. Consequently webauthors can access the GM API from scripts which come with the webpage. It's cross site scripting, so to speak, where one site is the webpage and the other is the (indistinguishable) GM context.

    9. Re:Why Uninstall? by sketerpot · · Score: 3, Informative

      This isn't a big deal. It means you lose: 1. Logging of GM script debug messages. Inconvenient if you're a script author, but not for anyone else. 2. Script-specific configuration values. I don't think these are commonly used, but they could be nice to have. Oh well, chances are your scripts will keep working. 3. Adding commands to the Tools->User Script Commands submenu. If, like me, you didn't know this submenu even existed, no loss. 4. Fancy GM_XmlHttpRequest. This is just like XmlHttpRequest but without domain restrictions. This may cause a few extensions to stop working (not many, but a few), but it also closes the security hole.

    10. Re:Why Uninstall? by DavidTC · · Score: 2, Interesting
      Which, BTW, is a stupid way to do it.

      I use an extension called NoScript, it disables Javascript by default, and I can turn it on per site, and even make it temporary. It can do that bar like you get when installing extensions or blocking popups, but I just keep the icon down in the status bar.

      It's even better than the 'per-tab' control you can get with various buttons, because it not only remembers each site, but it lets you turn on, say, slashdot.org, and not 'falkag.net', which right now apparently has scripts on this page.

      The problem is, unless I enable javascript on a page, the damn Greasemonkey scripts don't work on it either.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    11. Re:Why Uninstall? by Osty · · Score: 2, Interesting

      2. Script-specific configuration values. I don't think these are commonly used, but they could be nice to have. Oh well, chances are your scripts will keep working.

      If your scripts rely on GM_[set|get]Value, they won't work. The scripts may still run, but what value will they have? For example, I have a script that is only useful in the presence of GM_*Value and GM_xmlhttpRequest. Without that functionality, my script will add a useless bar to the page and never populate it with any data.

      4. Fancy GM_XmlHttpRequest. This is just like XmlHttpRequest but without domain restrictions. This may cause a few extensions to stop working (not many, but a few), but it also closes the security hole.

      It also breaks one of the biggest features of GM -- the ability to pull data from other sites and integrate it into the current page. Scripts like Book Burro are now completely useless. Security is important, and it is the right thing to do to remove this functionality while the GM folks look for a better fix, but it does make GM much less attractive (you're pretty much left with page cleanup scripts now that you can't pull data from other sites).

      Any idea why all of the GM_* functions had to go? I can see why GM_xmlhttpRequest could be a problem, but what's wrong with GM_log, or the GM_*Value functions?

  7. What should be done. by sykjoke · · Score: 4, Insightful

    The firefox guys should have realized that extensions are a HUGE security threat, possibly even worse than anything that's come out of IE. What they should have done is setup some permissions from the first place, so that you can allow or prevent extensions from performing sensitive operations. Something similar to the Java security model would have been good enough

    1. Re:What should be done. by cybersaga · · Score: 3, Insightful

      This is why Firefox makes you whitelist a site before downloading an extension.

      Forcing you to intentionally accept extensions is not a big security threat at all.

      This is just a bug. Bugs happen. It's been fixed already.

    2. Re:What should be done. by Buzz_Litebeer · · Score: 3, Insightful

      That is incredibly uninformed. IE can run Browser Helper Objects, and they can (many times) be installed completely silently. A cleverly written BHO can steal all information you are entering into your computer, even if it is unrelated to actual browsing, depending how clever the person is in writing it. They are a pain to uninstall as well. Extensions for firefox are uninstallible from a menu, and they are whitelisted before they ever get to you, so that you can avoid some of the fly by installs that BHOS enjoy.

      --
      If you don't vote, you don't matter, so don't waste your time telling me your opinion
    3. Re:What should be done. by Anonymous Coward · · Score: 2, Interesting

      I agree completely!

      I have stated it here before:

      Just like ActiveX controls proved a hole in IE, FireFox's extensions would eventually prove a hole in the XUL based 3rd party FireFox extensions arena now & this browser itself, & thus, your OS etc. as well via this gateway.

      This is/was 1 thing FireFox imo, had on Opera (my 'browsing weapon-of-choice' online because it wins the speed test comparisons between them all in the most areas typically, but also because it is the LEAST attacked browser as well that shows the fewest holes per year & is by default, just as feature-laden as IE or FireFox (in their defaults), perhaps even moreso in the latest 8.02)...

      BUT, now, that 3rd party development is starting to show some faults in it, like this one. Maybe, just maybe, history was the example in IE... of things NOT to do in browsers.

      BUT, on the other hand? ActiveX controls extensions of IE, &/or FireFox?? Give it a LOT more power/ability too!

      (Double-edged sword this topic, imo!)

      Sure, the 3rd party folks EVENTUALLY patch for it, but this is only 1 that's been discovered... how many others are there potentially?

      (Perhaps the Mozilla folks have to setup some kind of "Quality Assurance" test prior to users submitting their stuff to their pages for extensions to firefox if they don't have one already of somekind? Would this even help?? Who knows!)

      There are, after all, many hundreds of these things (firefox extensions, when I rarely use FireFox, it is loaded with 30 of them that I found useful/excellent, but some ARE slow to load & tend to slowdown FireFox unfortunately)

      Yes again: They DO tend to make FireFox alot more powerful than by default (but, load TOO many or the slower ones? You LAG, & bad @ startup)...

      This posting however, just again evidences what I personally thought would eventually show holes/vulnerabilities in FireFox...

      Just as ActiveX did for IE.

      APK

      P.S.=> Is this a "big deal"? Yes, & No... if the makers of it patched for it quickly?? Then not. If there was a large "Window of Opportunity for exploiting it" (relative term time-wise), then yes it was... depends on your viewpoint, & if in fact, you used this FireFox extension, right? apk

    4. Re:What should be done. by I+confirm+I'm+not+a · · Score: 2, Informative

      The firefox guys should have realized that extensions are a HUGE security threat

      The Firefox guys did; fortunately this has very little to do with FF extensions! It's an issue with GreaseMonkey User Scripts, which are javascript files run by the Greasemonkey extension. Extensions are OK; certain Greasemonkey user scripts *may* not be.

      For anyone who's never heard of GreaseMonkey - DON'T PANIC! It doesn't affect you: nothing to see here, move along, please.

      For folk who use GreaseMonkey, continue to exercise caution when you install user scripts (for non-GM people, user scripts are installed by visiting a javascript on the web, giving you the opportunity to read it) - READ THOSE SCRIPTS FIRST, PEOPLE!

      Apologies for the shouting, but this stuff's important. Just not that important.

      --
      This is where the serious fun begins.
    5. Re:What should be done. by sykjoke · · Score: 2, Insightful

      It is a problem with Firefox allowing GM to have such privileges. Do you always log in as administrator or root? Have you edited the source code of postgress so that is can also run as root? So why should Firefox give root to any extension that comes along?

    6. Re:What should be done. by westlake · · Score: 3, Informative
      Browser Helper Objects...can be installed completely silently...They are a pain to uninstall as well

      Microsoft's Anti-Spyware monitors the installation of BHOs. BHOs can easily be blocked or removed: MS Antispyware > Advanced Tools > System Explorers > Internet Explorer > IE BHOs.

    7. Re:What should be done. by Anonymous Coward · · Score: 2, Informative
      For folk who use GreaseMonkey, continue to exercise caution when you install user scripts
      This vulnerability has nothing to do with user scripts.

      EVERYONE WHO HAS GREASEMONKEY INSTALLED IS AT RISK!

      Malcious webpages can just hook into greasemonkey functionality, and use it to read local content, regardless of userscript. And then there's of course also the risk of untrusted userscripts doing bad things, but that is equivalent to untrusted extensions. Like the parent says, use caution, and don't install without reading the sourcecode first.

      Not that anyone ever does that for extensions. Not even the addons.mozilla.org people. Bad Firefox extensions! No cookie!
    8. Re:What should be done. by telecsan · · Score: 5, Insightful

      Even after you've installed an extension, you shouldn't be forced (by Firefox) to accept any and all behaviour it tries to produce. I should be able to install a toolbar and prevent it from calling home, for example. You should be able to set the permissions or at least the 'run-as' of the toolbar separately from the permissions of Firefox. Surely the security-conscious /. community should realize that.

  8. Fixed? by A+Dafa+Disciple · · Score: 2, Informative

    According to Firefox extensions site, you need to "uninstall or upgrade now." The post is from today.

    1. Re:Fixed? by notreallynas · · Score: 2, Informative
      From the GreaseBlog:
      Greasemonkey 0.3.5 is a "neutered" version of Greasemonkey, lacking any of the GM* APIs which make Greasemonkey scripts more powerful than regular HTML. This means that scripts which depend on GM* APIs will fail with Greasemonkey 0.3.5.

  9. Opera's answer... by TheJavaGuy · · Score: 2, Informative

    Time to try out Opera's User JavaScript.

    --
    Opera Watch - An Opera browser blog.
  10. What did they expect? by Nytewynd · · Score: 4, Interesting

    If you build an engine that allows you to write scripts that modify any page you view, there are obviously serious security flaws.

    Allowing scripts to open files and send them elsewhere is especially bad, but there was a huge security concern to me either way. I like the concept of GreaseMonkey, but choose not to install it.

    --
    /. ++
  11. More details on the exploit... by octaene · · Score: 5, Interesting

    Here are some more details from the posting thread, which explains why the exploit is so bad...

    This particular exploit is much, much worse than I thought. GM_xmlhttpRequest can successfully "GET" any world-readable file on your local computer.

    http://diveintogreasemonkey.org/experiments/localf ile-leak.html returns the contents of c:\boot.ini, which exists on most modern Windows systems.

    But wait, it gets worse. An attacker doesn't even need to know the exact filename, since "GET"ting a URL like "file:///c:/" will return a parseable directory listing. (And Mac users don't get to gloat either; you're just as vulnerable, starting with a different root URL.)

    In other words, running a Greasemonkey script on a site can expose the contents of every file on your local hard drive to that site. Running a Greasemonkey script with "@include *" (which, BTW, is the default if no parameter is specified) can expose the contents of every file on your local hard drive to every site you visit. And, because GM_xmlhttpRequest can use POST as well as GET, an attacker can quietly send this information anywhere in the world.

    The above information posted originally by Mark Pilgrim

    1. Re:More details on the exploit... by markov_chain · · Score: 2, Insightful

      OMG! I hope I don't get exploited... or the attackers may get hold of this exciting information:

      bin boot dev etc home initrd lib lost+found man media misc mnt opt proc root sbin selinux srv sys tftpboot tmp usr var

      --
      Tsunami -- You can't bring a good wave down!
    2. Re:More details on the exploit... by DavidTC · · Score: 3, Informative
      People who don't understand this security flaw need to SHUT THE FUCK UP.

      Greasemonkey 'adds' stuff to Javascript. Any page on the internet can use these additions.

      If you have Greasemonkey installed, and Javascript enabled (Greasemonkey is rather pointless without Javascript anyway.), you are at risk.

      You can't 'be safe' by only doing certain things, because the flaw is that any page on the internet can call Greasemonkey functions. (Any page that can use Javascript, at least.) It has nothing to do with you.

      It is possible to use Greasemonkey with the NoScript extension to disable Javascript globally and then re-enable it only on a few trusted sites...but no one uses Greasemonkey on 'trusted' sites, we use(d) it to hack up stupid-ass pages that had eight square inch of content per page with the rest ads and fancy graphics.

      If you absolutely require Greasemonkey to make some internal site work, and are willing to disable Javascript on the entire rest of the internet, NoScript might be worth a try. Otherwise, get rid of Greasemonkey, NOW.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  12. Here's TFA by RamboIII · · Score: 3, Informative
    Important Announcement

    A severe security issue has been discovered in Greasemonkey versions prior to 0.3.5 as well as the early 0.4 alphas which some people may have installed.

    Install Greasemonkey 0.3.5 or uninstall Greasemonkey immediately.

    More information on Greaseblog.

    Greasemonkey is a Firefox extension which lets you to add bits of DHTML ("user scripts") to any web page to change its behavior. In much the same way that user CSS lets you take control of a web page's style, user scripts let you easily control any aspect of a web page's design or interaction.

    For example, you could:
    Make sure that all URLs displayed in the browser are clickable links Improve the usability of a site you frequent Route around common and annoying website bugs Use the Coral content network selectively.

    Getting started:
    Install Greasemonkey 0.3.5. Learn how to use Greasemonkey. Find useful scripts.

    Greasemonkey was heavily inspired by Adrian Holovaty's site-specific extension for All Music Guide and the conversation which ensued after he published it. There were tons of sites I wanted to create SSE's for, but fully-fledged firefox extensions proved too cumbersome. I wanted it to be as easy to create an SSE as it is to write DHTML.

    The current maintainers are Aaron Boodman and Jeremy Dunck with the invaluable help of an awesome community of user script enthusiasts.

    For questions or comments about greasemonkey, please send a message to the greasemonkey mailing list. Copyright © 2000-2005. All rights reserved. Terms of Use & Privacy Policy.

    Notice hoe they avoid explaining the problem/solution. They just want you to see these new exciting features, and download it now!

    --
    Time is comparison of movement to other movement.
  13. Our Fault by Comatose51 · · Score: 4, Funny
    This is why God invented the tag.

    We can blame God for all kinds of things like hurricanes and Godzilla but it's a safe bet that we brought THAT scourge upon ourselves.

    --
    EvilCON - Made Famous by /.
    1. Re:Our Fault by PakProtector · · Score: 2, Funny
      This is why God invented the tag.
      We can blame God for all kinds of things like hurricanes and Godzilla but it's a safe bet that we brought THAT scourge upon ourselves.

      Hey, now! We all know perfectly well that Godzilla was a result of the United States dumping radioactives into ocean waters, part of their plan to keep on supressing Japan after the war. After all, if Tokyo hadn't been leveled by Godzilla every 6 months, Japan would have taken its rightful place as ruler of the world!

      --

      Edward@Tomato - /home/Edward/ man woman
      man: no entry for woman in the manual.
      "Qua!?"

  14. Re:Windows Feature? by phasm42 · · Score: 3, Informative
    --
    "No one likes working in a hamster wheel, and your shop smells of cedar shavings from here." - TaleSpinner
  15. Let's Throw MUD! by GuitarNeophyte · · Score: 2, Insightful

    Although the "average user" won't be using the various plugins, Microsoft will still point to this as one more reason to say that FireFox isn't secure. Sure, FireFox has it's bugs. We need to get fixing them.

    I'm not saying that FireFox is perfect. Obviously, it's not, and this article is a case in point. It's still the browser I use. For me, this is a warning to fix things or wait for them to stable up (oh yeah -- that mindset shown, I am a Debian user). But just like we use any little IE thing to say "See, IE is junk," this'll get used too.

    *sigh* The joys of conflict.

    Luke
    ----
    Smarten up your stupider-than-you coworkers, send them to ChristianNerds.com

    1. Re:Let's Throw MUD! by Zeinfeld · · Score: 4, Insightful
      Although the "average user" won't be using the various plugins, Microsoft will still point to this as one more reason to say that FireFox isn't secure. Sure, FireFox has it's bugs. We need to get fixing them.

      And the winner of the Slashdot "Who can be the first to blame Microsoft for a bug in FOSS is..."

      The problem is not bugs, the problem is that nobody designed their systems to deal with the real security threats presented in the Internet today.

      The principle cause of Microsoft's security problems today was their addiction to 'featuritis' in the 1990s. If you think that the open source community does not have the same problem you need to take a serious look at some FOSS programs.

      There is nothing that can't be fixed but first people have to realize that FOSS has just as much need to fix them. Everyone in the security community will tell you that making the source code available does not guarantee that your code will be secured. We have enough trouble getting engineers to review their own code.

      We need a new approach to writing secure code. Before that can happen a lot of FOSS people need to loose their complacency. Microsoft is not the enemy here, the criminal gangs are the enemy.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    2. Re:Let's Throw MUD! by The+Bubble · · Score: 2, Insightful

      I think that this bug is evidence of how intelligent Firefox's extention-based architecture really is. A severe security bug is discovered in a feature? I can disable it, and go on working. That feature can be updated, upgraded, and I can resume using it again, and I never had to think twice about changing browsers, or wait for the next version to come out (though, as I'd like to point out, an updated version of GreaseMonkey has already been prepared.)

  16. Re:Is that really a problem? by grasshoppa · · Score: 3, Funny

    Personally, someone could read my entire hard drive and it wouldn't bother me much. I don't keep sensitive information on my computer, because any computer connected to the internet should be considered insecure.

    Nice try Bill, we know it's you.

    --
    Mod me down with all of your hatred and your journey towards the dark side will be complete!
  17. Uninstall / Remove by dhanes · · Score: 2, Interesting
    After all of a quick 3 minute search of Pilgrim's site and Firefox, I can't find any directions as to how to actually uninstall or remove greasemonkey.

    Would anyone have that info to post?? Thanx

    --
    Wait, What?
    1. Re:Uninstall / Remove by AnObfuscator · · Score: 3, Informative

      Go to "tools", go to "Extensions", click on the greasmonkey extension and click "uninstall" or "update".

      --
      multifariam.net -- yet another nerd blog
  18. Rock paper cissors by Arthur+B. · · Score: 3, Funny

    Firefox burns greasemonkey cuz it's made of fat But Seamonkey beats firefox because it extinguishes the fire. Then Greasemonkey beats seamonkey because it can float in water AND walk on land. my 2.56 cents

    --
    \u262D = \u5350
  19. no, Time to stop browsing as root! by gwait · · Score: 2, Insightful

    Oh, wait I don't browse as root already!
    Guess it can't access "all" the files on my system then, can it?

    --
    Bavarian Purity Law of Rice Krispie Squares: Rice Krispies, Marshmallows, Butter, Vanilla.
  20. Possible solution - NoScript extension is great ! by CdBee · · Score: 5, Interesting

    I use Greasemonkey in conjunction with NoScript - an extension which prevents any site from using Javascript unless it is added to the whitelist maintained in the extension.

    To run a Greasemonkey script on a page you have to allow that domain or subdomain in NoScript. This prevents Greasemonkey being used on a rogue page as I wouldn't use a script on an uber-dodgy site anyway!.

    --
    I have been a user for about 10 years. This ends Feb 2014. The site's been ruined. I'm off. Dice, FU
  21. A HELPFUL TRANSACTION. by Anonymous Coward · · Score: 5, Insightful

    (MAN) Sirs, I am in dire need of a web-browser! The one thus furnished to me by Mr. Gates of Redmond is rickety and unsafe, and prone to inviting the most deadly of spy-ware into my parlor!
    (MOZILLA SOCIETY REPRESENTATIVE) Why, good sir, we shall help you forthwith! We have exactly the web-browser that you need! It has been engineered to the most careful of specifications, and its security is without compare!
    (MAN) Why then I shall have one immediately!

    (LATER)

    (RANDOM STREET URCHIN) Sir, I see that you have this day procured a web-browser, which I see under your arm. May I convince you to also take this complex contraption of my own invention, which will attach to your web-browser as a "plug in"?
    (MAN) What, what? An inscrutable device of unclear ultimate function furnished by a stranger of whom I know nothing? Yes, yes, why not. Now run along, lad.

    (LATER THAT NIGHT, THE CONTRAPTION PROVIDED BY THE STREET URCHIN EXPLODES, SETTING THE WEB BROWSER AFLAME.)

    (MAN) What's this? Oh, mama! The web-browser I have this very day recieved from the Mozilla Society has immolated, consuming my drapes and lighting my house aflame. They told me it was secure! Lies! Betrayal! Those Mozilla Society rapscallions! I'll give them what for!

    1. Re:A HELPFUL TRANSACTION. by patio11 · · Score: 2, Insightful

      Open source advocates do themselves no credit when they say "Spyware which takes advantages of weakness in the design of IE is Microsoft's problem, but spyware which takes advantages of weakness in the design of Firefox is the author's problem". If this were MSIE you can be 100% sure that somebody would be saying "Why, why, why does Windows even ALLOW users to run untrusted code?"

  22. Re:The next messge in the thread is worrisome by Anonymous Coward · · Score: 2, Informative

    Calm down? What that means is people will be alerted by the Mozilla update feature that an update is available. They can still not update. But this is a GOOD THING since not everyone who uses GM reads slashdot or the GM web site!

  23. Re:But, but, but by Koiu+Lpoi · · Score: 4, Informative

    You're correct. It was discovered by a white hat.

  24. Re:Is that really a problem? by ArsenneLupin · · Score: 2, Funny
    because any computer connected to the internet should be considered insecure.

    You know, there are also other OSes than windows...

  25. Um, you don't actually use Firefox do you? by mcc · · Score: 3, Informative

    It should be up to the individuals to decide if they want to make such significant mods to their system as purposefully crippling software.

    You mean like in Firefox, where when updates are available all the auto-update feature does is display a little "updates available" icon in a browser window, then offer to install the updates when you click the icon?

  26. If we were Microsoft by Felinoid · · Score: 2, Insightful

    "It's not a bug it's a feature" are quite likely words never actually spoken by any representive of Microsoft.
    However there is a reason for this attatude.

    Bug that makes it possable to run code on remote users box:
    Users say "Oh no bug bug. Get rid of it"
    Develupers say "Ohh feature feature keep it, expand it"
    Security experts say "Bug"

    If the develupers provide a strong enough argument the "bug" is classified as a feature and remains.

    --
    I don't actually exist.
  27. ING by samjam · · Score: 3, Insightful

    StudyING it (it takes time) and they HAVE found it is not secure, just like the millions of eyes are supposed to do.

    One of them is bound to notice, eh?

    So it works! Sweet!

    Sam

  28. Exactly! by GillBates0 · · Score: 2, Insightful
    I would've typed in an almost identical comment had I not bothered to RTFC.

    No matter how secure the core Firefox code is, it is all meaningless with the current extensions model. With the current model (or lack of one) a malicious (or plain buggy) extension can turn Firefox into a bigger threat than IE.

    From my understanding, Firefox extensions aren't restricted from doing I/O or listening on sockets/etc. What's to prevent somebody from writing a seemingly harmless extension which silently dumps all activity logs or other information to an outside listener?

    A Java type sandbox model, while a reasonable analogy would IMHO be overly restrictive for extensions, which need to be more closely tied into Firefox than most Java applets need to be to do all the cool things that they currently do (eg: the Tabbrowser Extension) .

    --
    An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
  29. it's not any file from your disk by lonedroid · · Score: 2, Interesting


    It seems rogue pages can read any file from your disk and send it to any site, using an XmlHttpRequest.

    Only if the browser has all the rights, which is a very dumb thing to do no matter the platform.

    On my main Un*x box, Firefox was installed in a normal user account (using the .tar.gz) and there's no way that a "Firefox expl0it" can access any file on my hard disk (and btw the risk for this particular exploit is zero: I don't use GM ;)

    I'm pretty sure that Firefox/GM installed in a non-privileged user account under Win2000/XP doesn't allow to access any file from the hard disk either.

    I'm not trying to defend poor coding/security practice made by people who certainly should know better, but it's simply misinformation to say that access to the files accessible from a user account is equivalent to "all the files on the harddisk".

  30. 1986 by Spazmania · · Score: 4, Informative

    In 1986 I wrote a Commodore 64 terminal program that allowed BBS' to download and run bits of assembly code onto the user's machine in order to enhance the user's experience. It took about 48 hours before someon posted a message that executed a jump to address 64738 -- system reset.

    Bad idea then. Worse idea now, no matter how much supposed security you surround it with.

    --
    Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  31. Maybe I'm clueless, but... by ded_guy · · Score: 4, Insightful

    I admit that I haven't yet tried out GreaseMonkey, but when I look at the exploit code it raises one really big question. Why isn't there some way to prevent non-user script from accessing the GreaseMonkey objects? Wouldn't this allow the user to retain all the ability they have now while rendering scripts from malicious sites harmless? Seeing as how GM is meant to be a means for the user to use scripts to modify pages, it seems very odd that anything outside of user script would be able to access its functionality.

    I realize it's likely due to the nature of Firefox's JS interpreter, but if this sort of separation isn't viable could someone enlighten me as to why?

    --
    In the future, all spacecraft will be made of cheese.
    1. Re:Maybe I'm clueless, but... by Rits · · Score: 4, Interesting

      Greasemonkey inserts the script directly in the pages, so the GM scripts have the same security context as the page itself. Or so I've understood, correct me if I'm wrong.

      In the really integrated solution like Opera has (as opposed to an extension like GM is), userscripts have their own security context. The really powerful functions in Opera's userscript are not available to the page author. All functions in GM, including the most powerful, are available to the page author, and Mark Pilgrim just found out this includes unlimited read access to your local file system.

      The GM developers are aware that this is a problem, but haven't developed a better way yet to inject the scripts in the page. So the newly secure release 0.3.5 removes the most powerful functions.

      --
      If you don't like having choices made for you, you should start making your own. - Neal Stephenson
  32. Playing in the sandbox by jfengel · · Score: 4, Insightful

    Why would you say that a sandbox model is overly restrictive? The Java sandbox model has many routes out; it means that you can specify what permissions an application has, not forbid all of them. The Java model comes with nearly all permissions set to "no", but they can be opened.

    That said, I haven't seen a really good way to manage permissions. It's just not practical for an applet to say, "In order to run this, you need these 47 permissions" and expect you to fix that. With cleverness the modeler could create roles with aggregates of permissions, so that you can say, "This app needs access to your browser UI" (like Tabbrowser).

    Still, that's asking the user to make a lot of security judgments based on trust. Some extensions/applets/ActiveX should be allowed to modify your hard disk; most shouldn't. How can the user tell?

    It's a hard problem, one that I don't have a good answer to. I know Microsoft's solution (based purely on a yes/no trust decision) sucks. But I'd say the problem isn't the over-restrictiveness of the sandbox, but the difficulty of asking the user to manage his/her sandbox well.

  33. Re:Isn't it the same? by prof_tc · · Score: 2, Insightful

    Its not a hole in Firefox....
    You choose whether or not to install a plugin.
    Firefox, without any extensions, is probably hundreds of times safer then IE. Comparing Firefox with a bad plugin installed to IE, which is full of holes out of the box, is like comparing a Ferrari with a flat tire to a old junker and saying the junker is better.

  34. Re:Isn't it the same? by Blitzenn · · Score: 4, Insightful

    IE's vulerabilites are admittedly in the same area. It is not that IE installs bad code, it is that it allows bad code to be installed. I don't see the difference. I am not defending IE at all, but Firefox is starting to quack like a duck too, it seems to me.

    Perhaps there is some credibility to the arguement that once usage of a software package becomes widespread enough, there will be people who find ways to use it to their (malicious) advantage, regardless of the built in security features.

  35. Hyperbole by RealProgrammer · · Score: 2, Insightful

    While some kind of "security" layer sounds nice, I'd like to know what you suggest, specifically. A popup box saying "this site is requesting permission to read file X"? User clicks ok, every time, and they quit looking at it after a while. Then you wrote this:

    a HUGE security threat, possibly even worse than anything that's come out of IE.

    • You can always uninstall the extension (but you can't uninstall part of IE)
    • An extension only affects the portion of the installed base that uses it
    • The model is:
      1. Put it out there
      2. Wait till it breaks
      3. Fix and repeat.

    There's really no way an extension to a Firefox app could get the penetration that IE had. Maybe AdBlock could get to 95% of the Firefox base, so if Firefox had 95% of the market, it could have the kind of numbers IE had in its heyday. Those are a couple of really big ifs, so I don't think your "worse than anything that's come out of IE" is at all justified. I'm not trying to hide behind obscurity, but just saying that your hyperbole is misplaced.

    How many IE users have been hit by spyware? 40%, 50%, something like that? Come on.

    --
    sigs, as if you care.
  36. Re:The next messge in the thread is worrisome by idonthack · · Score: 2, Insightful
    Computers connected to the internet are "protected computers" under the statute. Crippling the software under the guise of an "update" is illegal.
    Like when Microsoft released Windows XP SP2 and broke everybody's internet applications?
    ---
    Light is filtering down from above. Would you like to use DIVE?
    Generated by SlashdotRndSig via GreaseMonkey
    --
    Why is it that when you believe something it's an opinion, but when I believe something it's a manifesto?
  37. unsecure by zerocommazero · · Score: 2, Funny
    When are you people going to take the hint?! You've got to stop using unsecure browsers like Firefox with all its vulnerabilities. They call it Open Source for a reason!!!

    Internet Explorer is way more secure and reliable. I went to a porno site yesterday and a pop-up asked me if I'd like to learn how to increase my penis size! How'd they know?!!! They must be reading my mind!

    The next day, IE automatically took me to that site when I opened it up! In fact this page showed me a list of other sites I might like to visit like explicit hentai, rape videos, and scat! It was as if me and my browser mind-melded!

    I like that when I was asked to pay for the penis-enhancing pills that I was redirected to site 135.34.65.256 instead of having enlargeyourlittlemember.com in my history list (wanna surprise the wife..)

    It's been three months and I haven't got my pills yet. I think the postman is swiping them. (always wondered how he could steer his mail jeep and hand out mail at the same time.)

    Where was I? Oh yeah, Firefox is a more secure browser, just don't use monkey grease.

  38. Re:The next messge in the thread is worrisome by arkanes · · Score: 3, Insightful
    Tell you what. You sue the GM developer responsible, and then I'll give a shit about your whining. Security updates that disable insecure functionality are normal and accepted. Furthermore, the manual update process is at least as much an acceptance as an EULA is.

    Gator and Weatherbug are not illegal, sadly - the EULA as justification for inclusion has been upheld. The user is in fact getting a bug fix - the bug that allowed for a major security breach is being removed. You may not like that bug fix, but sucks to be you. GM is not disabled by this update and many scripts will continue to run. Insecure scripts will not.

  39. You're being silly. by mcc · · Score: 2, Insightful

    Huh?

    Calling it an update, when in actual fact its not

    I assure you, every user in the world who is not insane considers "removes a vulnerability that potentially allows any website to read your hard drive" an "update".

    I also assure you that if you want to engender trust among your users, removing as immediately as possible bits that would allow any website to read your hard drive is the way to do it.

    If upgrades that incidentally break features are illegal, then every single software company in the world would be in jail by now. The legal reference you are vomiting all over this comment tree has nothing whatsoever to do with what WebMonkey did today, it concerns something different.

    If you're so incredibly upset that a point release of a minor third-party extension for a minority web browser broke something minor in the process of fixing a truly huge and dangerous broken aspect of the previous point release, then the thing to do would be re-install the previous point release, not come make 30 posts whining about it on slashdot.

    the update mechanism is different under linux

    I have not used the firefox extention functionality under linux, but the documentation indicates you are flat out wrong here.

    In any case, if you wish to turn off the automatic update notify feature for extensions, instructions on how to do so can be found here.

  40. So Mozilla is no better than IE? by sheldon · · Score: 2, Insightful

    I'm gonna get troll rated for this, but whatever.

    So basically... Mozilla is just as much of an insecure platform as IE, because they allow plug-ins.

    Yeah, yeah.. It's Greasemonkey... it's some stupid add-in piece that you have to explicitly install.

    But that's also the way most spyware get's on IE. People get prompted "Please download and install this, and make sure you say 'Yes' when prompted is that ok?"

    and people do it...

    why? Because they are promised free porn, free poker, free music, or a free trip to Nigeria to collect their $10 million.

    Welcome to the real world!

  41. Re:FF's greatest strength also its greatest weakne by It'sYerMam · · Score: 2, Informative

    It's not that minimal, really. And if you stick to extensions from mozdev.org then there's an auditing body for you, as well. Most of the useful extensions are high profile, anyway, and so they are screened by more people, because you only really need a few to actually make Firefox significantly slicker (Adblock, Bugmenot, Web developer, some kind of Tab extension)

    --
    im in ur .sig, writin ur memes.
  42. -- MODS NOTE: Parent is openly trolling. See:-- by Anonymous Coward · · Score: 2, Informative

    Moderators please be aware. If you look at The parent poster's slashdot journal you will find that in the last two entries he (1) announces a "troll tuesday" dedicated to posting trolls and (2) directly links his post here today, with the header "flamewar!".

    It seems fairly clear, based on his journal entries in which he expresses an intent to troll and then links this post; and the nonsensical and extreme viewpoint expressed in the parent post, and the bait-and-switch method by which he argues one thing in the top-level post then switches to something entirely different in the replies; that "tomhudson" is purposefully trolling, then using his journal to show off his post to the troll community to gather support and possibly upmods.

    Please react accordingly.

  43. Re:FF's greatest strength also its greatest weakne by Shakrai · · Score: 2, Informative

    This is one of the reasons that I avoid FF. It's pretty minimal out of the box.

    Pretty minimal? WTF are you smoking? Firefox does everything for me right out of the box that I could ever ask it to do. I have installed it (total time including download less then a minute in most costs) on machines all over the place in lieu of using IE. I never have to download any extensions or plugins for it.

    In fact the only plugin that I have installed on FF at home is Macromedia Flash. Other then that it comes with everything I need.

    --
    I want peace on earth and goodwill toward man.
    We are the United States Government! We don't do that sort of thing.
  44. If a cold is no better than pneumonia... by argent · · Score: 4, Interesting

    Mozilla is just as much of an insecure platform as IE, because they allow plug-ins.

    Not quite.

    The big problem with IE is not just that it has a plug-in mechanism, but it has a plug-in mechanism that's based on the HTML control (the actual browser component) assigning the right to install plugins to an object (the web page) based on an ad-hoc security model that's based on the location the object is believed to originate. Certificates, security dialogs, and so on... these are layered on top of this, but basically the HTML control is responsible for figuring out if a "dangerous" action should be allowed with no more than hints from the calling applications, and a jargon-filled dialog box that the user has to decide on RIGHT AWAY.

    I get calls from my users all the time that are variants on "this dialog box came up and I hit 'yes' without thinking".

    So... the control is pervasive, it's used by lots of applications, the API can't be significantly changed without creating a mass upgrade day for every app that uses it, responsibility is placed in the wrong place, and the user interaction encourages mistakes.

    Firefox's extension mechanism has a similar problem with its installer, but:

    The extension installation mechanism is part of Firefox, not the Gecko HTML display object, so applications using gecko aren't automatically exposed as well.

    The Firefox extension API does not depend on the installer's behaviour, it's possible for Firefox to switch to a more secure download-and-install design without breaking any applications.

    The user interaction requires three separate steps, and there's no path through those steps that simply answering "yes" by reflex will result in the extension being installed.

    In addition, in Windows, there have been a number of attacks that involved tricking the HTML control into thinking that a remotely downloaded object was local... or even already installed. This approach is not possible in Firefox because instead of allowing plugins to run from anywhere except the places it thinks are dangerous, it doesn't allow plugins to run from anywhere except a specific directory that's got a randomly generated name in its path so it can't be targeted by a download.

    I would still recommend using a shell other than Firefox around a Gecko- or KHTML- based browser. I use Camino (Gecko) and Safari (KHTML) on Mac OS X, but I'm sure there are equivalents to these for Windows. But regardless, the exposure from using Firefox is so far less than using IE that if Firefox and IE are your only choices... use Firefox.

    I do not recommend using the Netscape browser, because of the way it allows the use of either Gecko or the Microsoft HTML control.

  45. Remember only world readable. by slack_justyb · · Score: 2, Informative

    I would like to first address a lot of the people who are taking this as a chance to really dog Firefox and the Open Source Community as a failure on their part.

    Because someone has discovered this problem, one can now fix the problem. That is the whole idea of Open Source and all that rot. If anyone would love to submit a patch for Windows 95 to make it run longer than 52.5 days, I'm waiting. It's a known problem, why isn't it fixed? Well because someone, somewhere said they weren't going to fix Windows 95 because it's too old. Which this is the case a lot in closed source. you know there is a bug and you'd like something to be done about it, but nothing will be done unless MS sees that a patch for the software is a cost justified.

    Also aside from the fact that this is an extension of Firefox, I know it's just as bad as if the package was faulty. Up till today I had never heard of this extension. So I'm not sure as to how widespread this problem is, but I'm guessing that good chunck of all Firefox users do not have GM.

    To top it all off, the writers of GM have issued a fix for their extension by means of version 3.5. Yes I know it breaks API compatibilty, which sounds like something MS would do, but just like what the Mozilla team did with IDN, they turned IDNs off until they could make a good way of handling them. Which the Mozilla team came up with a fix in a fairly decent amount of time. I find it highly possible that this peice of software will do likewise. As opposed to MS breaking things with SP2 and then telling all of the vendors to just get over it, (which I will agree that only a small amount, twenty or so, of vendors got 'left behind', so not horrible, just bad.)

    Now secondly, from the story, GM only returns results of files that are world readable (aka the Everyone group if you are a Windows person). Now, I'm not sure how everyone has their system setup so this could all vary from one person to another.

    In Linux my home directory (the one with all my private stuff) is only owner read, write, traversable (700 or rwx------).

    If I remember correctly, in Windows the C: (root) drive's premissions for the Everyone group is.

    -Traverse/Execute
    -List Folder/Read
    -Read Attributes
    -Read Permissions
    (I may have missed a few because I don't have a Windows machine handy)

    At no part is write premission granted to Everyone.

    Therefore, your OS is mostly secure to protect you from getting some form of malware on your system.

    However, this does allow someone to read data from your system if, and this is the big if, you set your private stuff as world readable (aka readable by the Everyone group.)

    Which as far as I know all of your cookies and history is stored somewhere in .mozilla (Linux) My Documents (Windows)

    Which as stated previously /home/$USER on my machine is (700 or rwx------) which prevents /home/$USER/.mozilla/firefox/* from being displayed (and just to be safe all things ~/.mozilla/* should be 700)

    Now if I correctly remember for Windows, My Documents, does not even have an entry for the Everyone group to do jack crap with. I know, gasp , Windows Permissions actually working for the user?!

    So this leaves the would be hacker mostly your system configuration (and not even the good parts) left open to be read. I know they can't read a bunch of my /etc folder (Linux's folder for configuration) because a lot of it is owned by root with 700 or 770 permissions. So that leaves for the most part things that a hacker could have already found out if they had just used nmap on my system. Same goes for Windows.

    I mean really, what good does it do one to only be able to read the boot.ini file??? "Ok, now I know you have two installs of Windows, or you use the Windows bootloader to load Linux for you (or what not.)" It's not like they can change it, only read it.

    This problem isn't a very high security threat if you have some wits about you, but it is a problem indeed and it needs to be fixed. However, this problem is being hyped up as if this was allowing world write access to your system, which is just not the case.

  46. The Firefox XPI model needs re-evaluation... by argent · · Score: 3, Insightful

    I would like to first address a lot of the people who are taking this as a chance to really dog Firefox and the Open Source Community as a failure on their part.

    I've been arguing that the Firefox XPI model needs to be re-evaluated from a security standpoint for some time now.

    1. Installing XPIs should not be initiated from a web page. They should be downloaded and manually installed, like any other application or application plug-in. This would allow any attacks that involve using the installer for privilege escalation to be eliminated.

    2. Expanded rights should not be granted to any javascript that has not been explicitly installed.

    3. As a corollary to this, any method that leads to an eval should, when run from a script that's part of chrome, unconditionally revoke those rights. A new method that explicitly evals code with greater rights with a name that makes it clear that it's dangerous can be added if it's actually necessary.

    1. Re:The Firefox XPI model needs re-evaluation... by slack_justyb · · Score: 2, Interesting

      From what I can gather you're asking the Mozilla team to change their current assumptions on how software should be install and how privileges work with the XPI system.

      I honsetly belive that the current rules in place by the Firefox developers are well minded and do a good job at keep malware base XPIs from getting into a system. However, I think this whole line of thought is a personal taste as opposed to something that the developers should take onto themselves.

      However, I would like to address your first point. Where you stated that XPIs should not be initiated from a web page.

      Which the point of this is to allow a cross platform installer. I would hate to think that if you made an extenstion for Firefox, you would have to write an installer for Linux, BSD, Windows, Mac OSX, Solaris, HP-UX, BeOS, SkyOS ... This solves that problem.

      Now I understand your concern. It's a very logical concern, but if a user goes to malwarefreaks.blowyourcomputerup.com and installs an XPI from there (even after all the popups that tell that user not to do so) and then the user's computer becomes unusable. Well, I find that the fault of the user and not the developers or the XPI system.

      There again. You have some really valid points but you can't keep a person from being a total idiot. I believe the defaults of Firefox give enough security with flexibilty.

    2. Re:The Firefox XPI model needs re-evaluation... by argent · · Score: 2, Interesting

      From what I can gather you're asking the Mozilla team to change their current assumptions on how software should be install and how privileges work with the XPI system.

      Yes, but by no means as great a degree as you seem to think.

      I would like to address your first point. Where you stated that XPIs should not be initiated from a web page.

      That's correct.

      Which the point of this is to allow a cross platform installer.

      It's not necessary to allow XPI to be installed by a remote web site to allow a cross-platform installer. You don't need to have files opened in a web page to have a cross-platform "open file". You don't need to have bookmarks opened in a web page to have a cross platform "install bookmarks". I'm not saying "don't use chrome and javascript to install a package", I'm saying "don't allow the installation process to be initiated from a webpage". Let the user select "install extension" from a menu, and then select the file they downloaded, and THEN the current installation mechanism can go forward.

      Because if by whitelisting a site you grant webpages opened from that site additional rights (the rights to initiate an install, and whatever other steps are necessary to reach that point) you open yourself up to an exploit using those rights from that site, either by injection through a link (as in the recent security fix) or by simple HTML injection through any form on that site.

      [I believe] the current rules in place by the Firefox developers are well minded and do a good job at keep malware base XPIs from getting into a system

      I don't. Most of the fixes in the post-1.0 security releases would not have been necessary if the design of Firefox was inherently safe. It's very close, but it's not quite there. Getting it there would not be difficult, nor would it reduce the flexibility of the system, it's just a matter of arranging things so that the default state of any "eval" operation (whether from a 'trusted' script or not) is 'untrusted', and that the operation in which a script's rights are revoked is immutably one-way.

  47. CAPs - a solution to access control problems? by matvei · · Score: 2, Insightful
    That said, I haven't seen a really good way to manage permissions. It's just not practical for an applet to say, "In order to run this, you need these 47 permissions" and expect you to fix that. With cleverness the modeler could create roles with aggregates of permissions, so that you can say, "This app needs access to your browser UI" (like Tabbrowser).

    I find it interesting that every application has to wrestle with these problems time and time again, instead of them being solved by the operating system. The reason for all this trouble is that the Access Control List security model is inherently flawed.

    Using ACLs makes us adjust permissions per user basis, while it is not the user who does (good or evil) things with the computer but the processes running on behalf of the user. Thus an application can (be tricked to) do malicious things with the user's full permissions - as if the user himself was actively and knowingly destroying his data, sending it over to an eavesdropper, etc. A correct approach would be to grant permissions to do a certain operation on a certain resource per process basis. This is what the capability based security is all about. (If I am mistaken, I hope someone more enlightened in CAP theory will correct me).

    I am amazed that none of the popular operating systems implement capability based security models, since they would eliminate Confused Deputy Problems like this.

    Some random links relating to Capability based security: