Slashdot Mirror


Apple and Google Fix Browser Bug. Microsoft Does Not. (bleepingcomputer.com)

Catalin Cimpanu, reporting for BleepingComputer: Microsoft has declined to patch a security bug Cisco Talos researchers discovered in the Edge browser, claiming the reported issue is by design. Apple and Google patched a similar flaw in Safari (CVE-2017-2419) and Chrome (CVE-2017-5033), respectively. According to Cisco Talos researcher Nicolai Grodum, the vulnerability can be classified as a bypass of the Content Security Policy (CSP), a mechanism that allows website developers to configure HTTP headers and instruct the browsers of people visiting their site what resources (JavaScript, CSS) they can load and from where. The Content Security Policy (CSP) is one of the tools that browsers use to enforce Same-Origin Policy (SOP) inside browsers. Grodum says that he found a way to bypass CSP -- technical details available here -- that will allow an attacker to load malicious JavaScript code on a remote site and carry out intrusive operations such as collecting information from users' cookies, or logging keystrokes inside the page's forms, and others.

78 comments

  1. At least they're being honest now. by Duckeenie · · Score: 5, Insightful

    Their products are insecure by design.

    1. Re:At least they're being honest now. by zieroh · · Score: 2

      It's not like Microsoft has ever been mistaken about security, right?

      Right?

      --
      People who say "sheeple" have about as much sophistication as an AOL user, and in fact are probably actually AOL users.
    2. Re:At least they're being honest now. by zieroh · · Score: 3, Funny

      You really need to stop smoking crack before posting on Slashdot.

      --
      People who say "sheeple" have about as much sophistication as an AOL user, and in fact are probably actually AOL users.
    3. Re:At least they're being honest now. by lucm · · Score: 2

      top 10 products with highest number of CVE:

      1 Linux Kernel Linux OS 1930
      2 Mac Os X Apple OS 1890
      3 Chrome Google Application 1453
      4 Firefox Mozilla Application 1438
      5 Iphone Os Apple OS 1274
      6 Android Google OS 1255
      7 Flash Player Adobe Application 1035
      8 Debian Linux Debian OS 1022
      9 Windows Server 2008 Microsoft OS 956
      10 Safari Apple Application

      https://www.cvedetails.com/top...

      --
      lucm, indeed.
    4. Re:At least they're being honest now. by Anonymous Coward · · Score: 0

      lets look at that linux kernel number. how many of those have been addressed? and within what timeframe?

      compare *those* numbers to that of microsoft's products... where the closed source nature makes it more difficult to even find the damn bugs in the first place.. that, on top of relying on microsoft, only, to fix instead of a legion of developers.

    5. Re:At least they're being honest now. by gnunick · · Score: 4, Informative

      Okay, since we're talking about recent history ("at the moment", as you said), how about we have a look at recent CVE "scores", not the all-time list that you pasted in?

      Here's the top of the "winners" list for 2017:

      1 Android Google OS 564
      2 Linux Kernel Linux OS 366
      3 Imagemagick Imagemagick Application 303
      4 Iphone Os Apple OS 290
      5 Mac Os X Apple OS 210
      6 Windows 10 Microsoft OS 195
      7 Windows Server 2008 Microsoft OS 187
      8 Windows Server 2016 Microsoft OS 183
      9 Windows Server 2012 Microsoft OS 176
      10 Windows 7 Microsoft OS 174

      But just for fun let's see #11:
      11 Windows 8.1 Microsoft OS 167
      (on the "all-time" list you pasted in, #11 would have been Internet Explorer)

      source:
      https://www.cvedetails.com/top...

      Aha! You're right, "it's not 1999" any more (in 1999, Microsoft occupied only 4 of the top 10 spots).

      So let's see now... if you add up all the CVEs for all Microsoft products in the top 10 (everyone else seems to want to pretend Windows 8.1 never existed, so let's go with that), Microsoft scores a dazzling 915 CVEs so far 2017.

      --
      I have no special gift, I am only passionately curious. --Albert Einstein
    6. Re:At least they're being honest now. by lucm · · Score: 2

      Those were "all time leaders". Here's the current year:

      1 Android Google OS 564
      2 Linux Kernel Linux OS 366
      3 Imagemagick Imagemagick Application 303
      4 Iphone Os Apple OS 290
      5 Mac Os X Apple OS 210

      --
      lucm, indeed.
    7. Re:At least they're being honest now. by gnunick · · Score: 1

      Hahaha! Nice job with your selective editing.

      Gee, in a comparison to the all-time top 10, why would you list only the top 5 for 2017?

      I think we both know the answer. The hell you didn't see 'em, indeed.

      --
      I have no special gift, I am only passionately curious. --Albert Einstein
    8. Re:At least they're being honest now. by sexconker · · Score: 1

      Why would you add them up across Windows7, 8, etc.? Just to get a bigger number by counting the same vulnerability multiple times?
      With that logic, you'd be counting each Android vulnerability once for each Android build it occurs in.

    9. Re:At least they're being honest now. by tomxor · · Score: 1

      Aha! You're right, "it's not 1999" any more (in 1999, Microsoft occupied only 4 of the top 10 spots).

      So let's see now... if you add up all the CVEs for all Microsoft products in the top 10 (everyone else seems to want to pretend Windows 8.1 never existed, so let's go with that), Microsoft scores a dazzling 915 CVEs so far 2017.

      You're missing the point, recent history or not... total CVEs discovered does not matter, all that matters is total number of unpatched, open source will always have more CVEs. This difference for once clearly stated in the headline. And the result is that if you want to use Microsoft products you are expected to use antivirus, because they would rather you keep bailing out water than bother pluging the holes, M$ most common answer is: "Wont Fix"

    10. Re:At least they're being honest now. by David_Hart · · Score: 1

      Okay, since we're talking about recent history ("at the moment", as you said), how about we have a look at recent CVE "scores", not the all-time list that you pasted in?

      Here's the top of the "winners" list for 2017:

      1 Android Google OS 564
      2 Linux Kernel Linux OS 366
      3 Imagemagick Imagemagick Application 303
      4 Iphone Os Apple OS 290
      5 Mac Os X Apple OS 210
      6 Windows 10 Microsoft OS 195
      7 Windows Server 2008 Microsoft OS 187
      8 Windows Server 2016 Microsoft OS 183
      9 Windows Server 2012 Microsoft OS 176
      10 Windows 7 Microsoft OS 174

      But just for fun let's see #11:
      11 Windows 8.1 Microsoft OS 167
      (on the "all-time" list you pasted in, #11 would have been Internet Explorer)

      source:
      https://www.cvedetails.com/top...

      Aha! You're right, "it's not 1999" any more (in 1999, Microsoft occupied only 4 of the top 10 spots).

      So let's see now... if you add up all the CVEs for all Microsoft products in the top 10 (everyone else seems to want to pretend Windows 8.1 never existed, so let's go with that), Microsoft scores a dazzling 915 CVEs so far 2017.

      Your calculation is also misleading. It's quite possible that a Windows CVE spans a number of Windows versions which would lead to counting the same CVE by up to 5 times. I'm willing to bet that the number of unique Windows CVEs is about a third the number that you arrived at.

    11. Re:At least they're being honest now. by gnunick · · Score: 2

      Why would you add them up across Windows7, 8, etc.? Just to get a bigger number by counting the same vulnerability multiple times?
      With that logic, you'd be counting each Android vulnerability once for each Android build it occurs in.

      Um, gee... where do I start? I mean really, do you see Android (or any non-Microsoft product) broken down by version in that list? It seems to me that for a (lowercase) apples-to-apples comparison, adding up the counts for every version of Windows would be the only fair way to compare it to any OS (or Kernel) which isn't listed with a similar version-by-version breakdown.

      In any case, the total number of CVEs for Windows in the top 10 had little to do with the premise of my post, which was a rebuttal to an intentionally misleading post that tried to back up the ridiculous claim that "[a]t the moment, the security of Microsoft products is vastly superior to that of Google and Apple" by posting a part of an all-time list of vulnerabilities (which conveniently only includes one Microsoft product in the top 10). Well, the moment that I'm living in resides firmly in 2017. Once again, the 2017 list is here: https://www.cvedetails.com/top...

      I have no idea if cvedetails.com's numbers are in any way reliable. lucm cited them as "proof" of how fuckin'A-awesome Microsoft is these days, so it seemed fair to turn their source around to disprove the original, ridiculous, premise.

      But hey, since the OP's bon mot was obliquely attacking a specific vendor, not a product... let's assume cvedetails.com's numbers are somewhat accurate, and scroll to the bottom of https://www.cvedetails.com/top... that lucm originally linked to, where you'll see this juicy heading:

      Total Number Of Vulnerabilities Of Top 50 Products By Vendor

      There's a pretty bar chart there, but here is the sorted data list:

      #1 Microsoft 8528
      #2 Apple 5135
      #3 Adobe 4167
      #4 Mozilla 3279
      #5 Google 2708
      #6 2279 Oracle
      #7 1930 Linux
      #8 1373 SUN
      #9 1022 Debian
      #10 855 Canonical
      #11 784 Novell
      #12 560 PHP
      #13 466 Wireshark
      #14 452 Cisco
      #15 430 Fedoraproject
      #16 426 Redhat
      #17 364 Imagemagick

      --
      I have no special gift, I am only passionately curious. --Albert Einstein
    12. Re:At least they're being honest now. by gnunick · · Score: 1

      No, I'm not missing the point. You're totally right.

      But there is no run-down of patched-vs-unpatched status listed on that site, the source of a ridiculous argument that I was rebutting. My only point was that his (?) argument was ridiculous. Sorry to have provided a red herring by doing any dubious math.

      --
      I have no special gift, I am only passionately curious. --Albert Einstein
    13. Re:At least they're being honest now. by sysrammer · · Score: 3, Insightful

      Your calculation is also misleading. It's quite possible that a Windows CVE spans a number of Windows versions which would lead to counting the same CVE by up to 5 times. I'm willing to bet that the number of unique Windows CVEs is about a third the number that you arrived at.

      I'll bet you'd win. This indicates that MS doesn't fix their bugs over multiple releases.

      --
      His ignorance covered the whole earth like a blanket, and there was hardly a hole in it anywhere. - Mark Twain
    14. Re:At least they're being honest now. by gnunick · · Score: 1

      Your calculation is also misleading. It's quite possible that a Windows CVE spans a number of Windows versions which would lead to counting the same CVE by up to 5 times. I'm willing to bet that the number of unique Windows CVEs is about a third the number that you arrived at.

      Very true, but the premise of my argument was in the previous sentence. So sorry I included that last line. My argument required no calculations.

      To return the point of discussion, I suggest you scroll to the bottom of https://www.cvedetails.com/top... where you'll see the list of Total Number Of Vulnerabilities Of Top 50 Products By Vendor for 2017. I don't know how cvedetails.com does its math (nor do I know why they break down Windows by version, but not Android, etc.). Maybe they're also double-counting CVEs that span multiple Windows versions. Maybe they're doing the same with Android, macOS, etc. It's still an interesting set of data to discuss.

      Anyway, if I wanted to make a serious argument about this I'd do some real research into the data, the methodology of the data source(s), and clearly document my own methodology. I sure as hell wouldn't use data from a single web site whose reliability is a complete unknown to me.

      --
      I have no special gift, I am only passionately curious. --Albert Einstein
    15. Re:At least they're being honest now. by bondsbw · · Score: 1

      They break down Windows by version (unlike the others on the list), so they show as the next 6 items. But those versions are all based on the same code. They tend to share most exploits and fixes for versions that are supported in the same year.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    16. Re:At least they're being honest now. by Zemran · · Score: 1

      It is more than a little disingenuous that they list "the Linux kernel" and "OSX" as single items yet split Windows into separate versions to minimise its ranking. If you add the separate versions of Windows together as they have done with Linux and OSX, Windows goes off the scale.

      --
      I love stacking my barbecues in the shed at the end of summer - you can't beat a bit of grill on grill action.
    17. Re:At least they're being honest now. by Anonymous Coward · · Score: 1

      They break down Windows by version (unlike the others on the list), so they show as the next 6 items. But those versions are all based on the same code. They tend to share most exploits and fixes for versions that are supported in the same year.

      This; the comments we get from the MS shills in these threads are almost worse than the bugs themselves. Although it's much better than Windows I don't want to defend Linux because OpenBSD is better in some ways and the Linux people should learn more from that, however Linus doesn't try to pretend there are five different products called Linux to try to change the order of the lists. He also doesn't pay trolls to come around forums lying about his product. If the producer of a product has to lie about the security of their product then it's maybe a hint to use a different product. You can be pretty sure they won't tell you when there's a serious problem.

    18. Re:At least they're being honest now. by slashrio · · Score: 1

      ...that will allow an attacker to load malicious JavaScript code on a remote site and carry out intrusive operations such as collecting information from users' cookies, or logging keystrokes inside the page's forms, and others.

      Yeah right, sounds like Microsoft indeed.

      --
      "Trump!!", the new Godwin.
    19. Re:At least they're being honest now. by Cley+Faye · · Score: 1

      That's the number of publicly known/published vulnerabilities. We know (and it has been proven true) that a lot of vulnerabilities are secretly kept when discovered.
      Looking at it another way, I could say "look at how many flaws were fixed in the linux kernel, Mac Os X, Chrome and Firefox, and look at how many were fixed in MS products". Listing CVE says nothing about the actual number of vulnerabilities, only about their disclosure.

    20. Re:At least they're being honest now. by gweihir · · Score: 1

      Meaningless statistic is meaningless. And the one posting it is stupid.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    21. Re: At least they're being honest now. by dougdonovan · · Score: 1

      blame the ceo from india.

    22. Re:At least they're being honest now. by ElizabethGreene · · Score: 1

      Is it common for vendors other than Microsoft to file a CVE for flaws that are discovered internally even if there is no public release and telemetry indicates no exploits in the wild, or for privately disclosed vulnerabilities with no public release?

      This is not trolling; I'm actually curious to know. If that's not a common practice then it would be difficult to make an apples-to-apples comparison.

      (I work for Microsoft, but this isn't part of the work I normally do.)

    23. Re:At least they're being honest now. by Cley+Faye · · Score: 1

      No idea, but that's the point. Citing CVE (or any equivalent) listings as a "security gauge" is silly one way or another. And even if such list was relevant as to how secure a piece of software is, it would still be irrelevant in the real world, because you'd have to take into account how feasible each vuln. is, how effective it is, and how many systems are at risks.
      The main difference between closed-source and open-source here is that one allows for more eyeballs than the other; it doesn't mean that more people will actually look, find, fix vulnerabilities, nor that such vulnerabilities will be easier/harder to exploit in the real world, and how useful they'll end up to be. There's just too much variable to say "X is better/worse than Y" in such absolute way.

    24. Re: At least they're being honest now. by Anonymous Coward · · Score: 0

      Can image magic be converted to JavaScript llvm and run entirely in the browser? No more security risk, boom, just cured 300 CVEs.

    25. Re:At least they're being honest now. by tomxor · · Score: 1

      Ah ok... yes I couldn't find any stats about the state of open CVEs either, which is quite frustrating.

    26. Re:At least they're being honest now. by lucm · · Score: 1

      No idea, but that's the point. Citing CVE (or any equivalent) listings as a "security gauge" is silly one way or another.

      As opposed to just say "there must be secret bugs they don't tell us about"? How do you rank that? Arbitrary suspicion factor based on your own guesswork?

      --
      lucm, indeed.
    27. Re:At least they're being honest now. by lucm · · Score: 1

      Meaningless statistic is meaningless. And the one posting it is stupid.

      Then why don't you provide meaningful content instead of just bitching about things? Oh wait, I know why.

      --
      lucm, indeed.
    28. Re:At least they're being honest now. by zieroh · · Score: 1

      top 10 products with highest number of CVE:

      You use data like a drunk uses a lamp post: for support, rather than illumination.

      You're also a dishonest shill. Go fuck yourself.

      --
      People who say "sheeple" have about as much sophistication as an AOL user, and in fact are probably actually AOL users.
    29. Re:At least they're being honest now. by Cley+Faye · · Score: 1

      I don't rank that. I don't have to. I wrote (but you omited that part in your quote) that there's no absolute way to say that one piece of software is better than another security wise, and that the only thing openness bring to the table is the ability for anyone to look into it.
      I didn't say (here or anywhere else) "there must be secret bugs they don't tell us about" so I don't see why you're asking me this, aside from trying to stir a fruitless "discussion".

    30. Re:At least they're being honest now. by gweihir · · Score: 1

      You make one mistake here: You think that educating the likes of you is worthwhile. I have tried and know better. Arrogant and stupid is sure-fire way to become resistant to insight.

      Just one point: Anybody with some actual understanding knows that counting-metrics only make sense if the things counted are quite similar. Even a brief look at some random sample of CVEs immediately shows that this is not at all the case here and that counting is meaningless for the case at hand. Hence anybody promoting a counting-metric here is extremely disconnected from reality (or a big, fat liar) and any attempt at educating such a person is consequentially futile.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    31. Re:At least they're being honest now. by lucm · · Score: 1

      Hence anybody promoting a counting-metric here is extremely disconnected from reality

      Actually, it's people who say "counting-metric" that are disconnected from reality since it means nothing. Is it some kind of direct translation from Polish or whatever retarded language you speak?

      Anyways, there's no reason for you to throw a tantrum. Why don't you remove the stick you've got up your ass and contribute something to the discussion? You're not funny, you're not witty, and you're not good at being smug; stick to real content.

      --
      lucm, indeed.
  2. Good thing by Billly+Gates · · Score: 1

    Because Edge == IE 6 and it is not like Google ever refused to fix a bug while MS did first.

    Why am I ever bother writing a reply here?

    1. Re:Good thing by Snotnose · · Score: 1

      Why am I ever bother writing a reply here?

      A) You're drunk
      B) You're "compiling"
      C) You're putting off something you need to do but don't wanna

    2. Re:Good thing by lucm · · Score: 1

      A) You're drunk
      B) You're "compiling"
      C) You're putting off something you need to do but don't wanna

      Here's the 2017 version.

      A) You're triggered
      B) You're "docker pulling"
      C) You've withdrawn from real world interaction

      --
      lucm, indeed.
    3. Re:Good thing by slashrio · · Score: 1

      D) You're Dutch.

      --
      "Trump!!", the new Godwin.
    4. Re:Good thing by Dutch+Gun · · Score: 1

      Ya got me.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    5. Re:Good thing by slashrio · · Score: 1

      A few years ago an older guy from Holland, therefore a Dutch guy, while they call their country The Netherlands -- pfff, can it be any more complicated? -- called me a 'snotneus'.
      I said: "What?". And in bad English he said: "snotnose".
      Maybe even it was you. ;)

      --
      "Trump!!", the new Godwin.
    6. Re:Good thing by Dutch+Gun · · Score: 1

      If it was me, I likely would have called you a kleine snotneus. But I think that insult may be a genetic trait of the Dutch, along with thriftiness. You know how copper wire was invented, right? Two Dutchmen were fighting over a penny...

      --
      Irony: Agile development has too much intertia to be abandoned now.
    7. Re:Good thing by slashrio · · Score: 1

      First, it were two Scotch men, and second: 'kleine' (= little) would on average be correct as the Dutch tend to be the tallest people in the world (again, on average).

      --
      "Trump!!", the new Godwin.
  3. Really, Edge? XSS-vulnerable by design? by intellitech · · Score: 4, Interesting

    An attacker only needs to open a new page via the “_blank” method and use the document.write function to write malicious code inside this page before loading the actual content. The malicious content — the code to execute a banal XSS attack — remains, and helps the attacker bypass CSP protections.

    Just choked on my coffee after reading that. What possible use case could there be for allowing a blank page to even run javascript for document.write in the first place?

    --
    vos nescitis quicquam, nec cogitatis quia expedit nobis ut unus moriatur homo pro populo et non tota gens pereat.
    1. Re: Really, Edge? XSS-vulnerable by design? by corychristison · · Score: 2

      I suspect Microsoft relies on this "feature" in one of their products somewhere...

    2. Re: Really, Edge? XSS-vulnerable by design? by Monster_user · · Score: 1

      Is there some archaic manner of loading certain sites which requires they be loaded into a blank page? Or is there some requirement of a link somewhere, which Microsoft provides support for, that cannot be loaded with different restrictions by any other means than an exploit? Something about Microsoft thinks users are to dumb to tie their own shoes perhaps?

    3. Re: Really, Edge? XSS-vulnerable by design? by Monster_user · · Score: 1

      Office 365?

    4. Re:Really, Edge? XSS-vulnerable by design? by Kjella · · Score: 1

      Just choked on my coffee after reading that. What possible use case could there be for allowing a blank page to even run javascript for document.write in the first place?

      I can't begin to phantom where the thought process comes form, but developers do the stupidest shit to make things work right now. Whether it's documented behavior, undocumented behavior, bugs, unintentional side effects, race conditions or whatever Microsoft has probably found that some developers have used this in a non-malicious way because drumroll it works. And that's really the whole of the story, if you break it you don't just break malware authors you break some website that paid idiot developers or cheap-ass outsourcing company for it. Then the get angry at Microsoft because it worked before, so they keep the broken behavior. It's not gone even though IE6 is finally exorcised.

      --
      Live today, because you never know what tomorrow brings
    5. Re:Really, Edge? XSS-vulnerable by design? by lucm · · Score: 1

      It's not clear in the description (I suspect the person who wrote it doesn't know how web pages work) but this just means opening a link that has a "_blank" target (new window/tab).

      This is just clickbait as usual.

      --
      lucm, indeed.
    6. Re:Really, Edge? XSS-vulnerable by design? by Anonymous Coward · · Score: 0

      Read the tech details of the bug

    7. Re:Really, Edge? XSS-vulnerable by design? by The+MAZZTer · · Score: 1

      Well I can see poorly coded websites doing that to programmatically build up frames. Yes, writing JAVASCRIPT into a frame is odd, but I could see it happening. But when you navigate a frame everything that was in the old page should be unloaded. Old JavaScript, especially from a different origin, should not continue to run!

    8. Re:Really, Edge? XSS-vulnerable by design? by WaffleMonster · · Score: 1

      An attacker only needs to open a new page via the âoe_blankâ method and use the document.write function to write malicious code inside this page before loading the actual content. The malicious content â" the code to execute a banal XSS attack â" remains, and helps the attacker bypass CSP protections.

      Just choked on my coffee after reading that. What possible use case could there be for allowing a blank page to even run javascript for document.write in the first place?

      TFA is weak on details... what this all seems to be about has been known for a very long time.

      By blank I assume they mean an HREF with a TARGET of _blank but not really limited to blank just any target that opens a new window.

      What happens is when you link to the remote site if that site is malicious it can call back into the web page that opened it using "opener" like JS reference crap and modify or do shit in the window that called you.

      For example your banking website provides a list of hyperlinks to third party sites. One of the sites it links to happens to be prettypleaserobmeblind.org

      If hyperlink is HREF = prettypleaserobmeblind.org then you go to the new web page with no cross site implications. It doesn't matter if you open the link in a new window or tab.. your safe...

      Yet instead your bank adds TARGET=_blank to the prettypleaserobmeblind.org hyperlink. The page is now always opened in a new window/tab because they want to keep you on the site... as a result the destination site can now fuck with referring site via javascript opener back references under certain conditions to for example transfer all of the cash in your bank account to themselves.

      I ASSume that's what this is about. My personal opinion anyone (MS) who defends this type of behavior has a screw loose in their heads. I suspect most web developers are clueless about it... nor does there seem to be causal connection that would lead even a very careful person to infer relationship.

      While there is always some merit in the should have known better category technology that is inherently so treacherous to use seems rather counterproductive to me.

      I know when I learned about this I was ticked off... about as ticked off as when I learned all browsers intentionally break secure TLS version negotiation. Amazing the things I implicitly "assume" without questioning that turn out to be false... perhaps I'm just careless.

    9. Re:Really, Edge? XSS-vulnerable by design? by gustygolf · · Score: 1

      You can build a new window altogether in JavaScript, apparently, with no HTTP requests taking place. I think this is what your quote refers to.

      See the javascript at e.g. sheldon brown's bicycle gear calculator page, line 422 (function showit()) and forward.

      It basically uses document.write to build the whole pop-up results window.

      (Yes, I was surprised to learn that such a thing was possible.)

      --
      "Slow Down Cowboy! It's been 58 minutes since you last successfully posted a comment" -- slashdot, driving users away.
    10. Re:Really, Edge? XSS-vulnerable by design? by Cley+Faye · · Score: 1

      Opening a page with "_blank" target doesn't open a blank page; it open a page in a new tab/window. It's super common, and is often used to open link to external sites without losing the current page (it's somewhat seen as a UX nightmare for some people).
      So it's not just allowing a blank page to run foreign JavaScript, it's allowing any real page, following "correct looking" URL to run foreign JavaScript.

      For reference, an "about:blank" is what you'd want if you want to open a blank page. But the article clearly state "_blank", which is different.

  4. Genuine problem by Anonymous Coward · · Score: 2, Informative

    The attack is to open a blank page in JS, insert your malicious code, then load the victim website. Oh look, your malicious code can run.

    MSRC needs a bigger bat to force the IE team to fix this. But they have little influence in the company, which is why logging out of Microsoft websites doesn't invalidate your cookie; you can still use that old cookie to stay logged in. By Design, of course.

    1. Re: Genuine problem by Anonymous Coward · · Score: 0

      So all you need to do to compromise someone's gmail Gmail is...
      1) Hack their PC or the Gmail web host and then
      2) use this document.write attack?

      Why is step 2 needed again?

  5. Where? by wonkey_monkey · · Score: 1

    technical details available here

    Here? Where?

    For an internet news site you sure do have a shitty grasp of how the internet works.

    --
    systemd is Roko's Basilisk.
    1. Re:Where? by fisted · · Score: 1

      grasp of how the www works.

      FTFY

    2. Re:Where? by Anonymous Coward · · Score: 0

      Step 1) Click the link in the summary to the article.

      Step 2) Click the link in the article.

      For someone reading an internet new site, you sure fo have a shitty grasp of how the internet works.

    3. Re:Where? by tepples · · Score: 1

      With firewalls in so many places blocking everything but 443 and 80 out, and with device makers blocking native apps from their walled gardens based on ambiguous content criteria, www is the Internet as end users experience it.

  6. Usually it's Apple... by Ecuador · · Score: 1

    Huh, usually it's Apple with the "Broken As Designed stuff, I guess Microsoft is playing catch up in that area too ;)

    --
    Violence is the last refuge of the incompetent. Polar Scope Align for iOS
    1. Re:Usually it's Apple... by Anonymous Coward · · Score: 0

      One example provided and suddenly it's "usually". Is English not your first language?

    2. Re:Usually it's Apple... by Ecuador · · Score: 1

      As a software engineer, it was a common pattern when I was working with iOS. The example was one that came quickly to my mind in a form that I could easily search and post. I even had issues as a user, e.g. for about 2 years Apple had broken support if you had a Mac Pro with upgraded graphics and a multi-monitor setup with a mix of landscape and portrait mode monitors. Their reply to the bug reports was something akin to "if you have that kind of setup, you're doing it wrong". Of course you could also say that Microsoft has entire OSes "bad by design" (Vista, Win 8 etc) ;) And, to answer your question, no, English is not my first language, but I usually get by...

      --
      Violence is the last refuge of the incompetent. Polar Scope Align for iOS
  7. Well, it's only Edge by JohnFen · · Score: 1

    It's only Edge, so hardly anyone will be affected.

  8. windows 10 S you fail again just wait for EU smack by Joe_Dragon · · Score: 1

    windows 10 S you fail again just wait for EU smack down.

      iOS is locked to WebKit

  9. Safari not patched by DontBeAMoran · · Score: 1

    If you don't use the latest macOS version, you can't upgrade to the latest version of Safari.

    --
    #DeleteFacebook
  10. Option by Anonymous Coward · · Score: 0

    Where did the browser option "load only from origin site" go?

  11. MS stop keeping IE features. by bongey · · Score: 0

    Edge is suppose to be NEW browser but from the mozilla/firefox page it is one of those none standard IE "features". https://developer.mozilla.org/...

  12. Re:At least they're being honest now. NIGGER FUCK! by ddtmm · · Score: 1

    TL:DR

  13. I think Microsoft is right by Anonymous Coward · · Score: 0

    If your site is already outputting the necessary CSP headers and sanitising it's HTML correctly, I find it hard that you'll get your malicious JS payload to even invoke let alone open up a new blank page. Just sayin'.

    If the attacker is already able to run JS from your page then you have other issues.

  14. Possible NSA hacking vector by Anonymous Coward · · Score: 0

    If they want us to believe they aren't in cahoots with the NSA they should patch anything that vaguely smells of NSA.

  15. Re:At least they're being honest now. NIGGER FUCK! by Anonymous Coward · · Score: 0

    No kidding. "Brevity is the soul of wit."

  16. Re: At least they're being honest now. NIGGER FUCK by Anonymous Coward · · Score: 0

    Lol gn from outer space is a funny movie.

  17. Re:At least they're being honest now. NIGGER FUCK! by Anonymous Coward · · Score: 0

    At least update the irc servers you are putting in this. Those two servers, irc.secsup.org and irc.easynews.com haven't existed on EFnet in probably over a decade...

  18. Not just Microsoft by Anonymous Coward · · Score: 1

    sure, this time the people at NSA and CIA gave a court order to the sorry people at Microsoft, and they weren't allowed to fix the bug, but there are a dozen of these hiding in the other browsers, kept there by the same kind of court orders.

    If it's American, then it's back-doored by design. That's what you need to start telling people.

  19. Same-Origin Policy is definitely broken by design by Anonymous Coward · · Score: 0

    Annoys the heck out of me. Came across this on Edge and I was floored that hobo.homeless.com got access to all of homeless.com's cookies. I had to put in a few lines in my cookie saver/getters that append "hobo" to the front automatically based on URL.

    Those are of course made-up names.

  20. of course not! by Anonymous Coward · · Score: 0

    This is an integral part of windows telemetry

  21. pinterest is that way ---> by lucm · · Score: 1

    You use data like a drunk uses a lamp post: for support, rather than illumination.

    I'm sure you've been waiting for an opportunity to shoehorn that little inspirational nugget in one of your comments. Unfortunately, it doesn't work as well as you would have hoped because

    1) it sounds as corny as the text in a discount Hallmark Get Well Soon card
    and
    2) I didn't "use data", I merely copy-pasted stuff from the first result that comes up when one googles "top 10 cve", which even by your self-righteous, biased standards can hardly be construed as being dishonest

    I don't want to prevent you from living in that tinfoil hat fantasy land where every piece of information you see that doesn't support your preconceived ideas must be planted by some "shill" (if such thing even existed for real on Slashdot). The world is a beautiful mosaic and irrational angry tools like you are part of it. Just try to avoid leaking your Pinterest material in your Slashdot comments and everything will be fine.

    --
    lucm, indeed.
  22. Re:pinterest is that way --- by zieroh · · Score: 1

    I'm sure you've been waiting for an opportunity to shoehorn that little inspirational nugget in one of your comments.

    I rarely have to wait for very long before some hapless turd wanting to score snarkpoints on [_fill_in_discussion_forum_here_] ambles along and demonstrates a piss-poor understanding of what facts are and what they mean. I've used the term many times before.

    Unfortunately, it doesn't work as well as you would have hoped because [meaningless argle-bargle]

    Get over yourself. It was a direct hit. The only one here who maybe doesn't understand that is you.

    2) I didn't "use data", I merely copy-pasted stuff from the first result that comes up when one googles "top 10 cve"

    A meaningless distinction if ever there was one.

    As others have noted, Windows is largely split across multiple versions, while virtually nothing else is. To willfully ignore that is to willfully misuse the facts in your pursuit of snarkpoints. And for that, you suck, oh-ohhhh!

    --
    People who say "sheeple" have about as much sophistication as an AOL user, and in fact are probably actually AOL users.