News for hackers. Stuff that matters.
Re:Google discloses another Windows security issue after dea... by RogerL on Thursday January 15, 2015 @08:45PM (#8896796)
So there are 3 issues [1] against OS X, released a while ago, and one against Microsoft. Why the HN focus on the Windows bugs? At least Microsoft is communicating with Google, and have patches planned, just not on the exact timeline of the arbitrary 90 day deadline. Is there something about the OS X ones that doesn't warrant the same exposure/discussion?

[1] https://code.google.com/p/google-security-research/issues/li...

Re:Google discloses another Windows security issue after dea... by drzaiusapelord on Thursday January 15, 2015 @10:21PM (#8897086)
Because a Windows zero-day is a major risk to our economic system as our business and governments infrastructures run on MS products for the most part. OSX just doesn't have that level of install base and for the most part its installed on consumer/residential equipment. Heck, most OSX shops I've been part of have bog standard Windows AD on the back-end. Windows, good or bad, is everywhere that matters.

Google seems to think Windows is a poorly written php app where you can just change a line and walk away. Windows testing has to be top notch and handle a huge about of 3rd party software, libraries, and drivers. The 90 day deadline really speaks to how web devs think and not how application engineers with massive install bases on a variety of equipment and running a variety of software think.

It does piss me off to be honest. MS isn't saying no to the updates its just saying, "We're doing them in 100 days, not 90 as out of band patches are really bad for the ecosystem and we need more time to certify our changes." Google is saying, "Fuck you. Buy an android tablet, microserfs."

Imagine if Google found the Kaminsky DNS bug. The internet would have melted on day 91 when google told everyone, "Sorry, too bad." I think this kind of "fuck you" disclosure should only be for attacks that have been demonstrated to be in the wild. Now they will be in various crimepaks, botnets, and trojan droppers within hours.

Re:Google discloses another Windows security issue after dea... by mikekchar on Thursday January 15, 2015 @11:02PM (#8897204)
I used to work on telephone switches. We had 31 million lines of code. I can't remember the entire details since it was over a decade ago, but I believe Bellcore required us to deploy fixes for 70% of all reported bugs within 30 days. We were a huge, fat-ass company with 5000 programmers working on the same project and managed this. 90 days is a lifetime to fix a security problem.

The point behind having a deadline before publicly disclosing is that if one person has discovered a security problem, then some other people probably have as well. It is fair enough to give vendors time before you make disclosure but if the vendor is moving too slowly -- for whatever reason -- you want to give the consumers a chance to implement their own security work around. Because if you don't they are vulnerable.

Giving Microsoft 90 days to fix an issue is fine. They can prioritize it anyway they want. If they think it is super urgent, they can almost certainly get a fix out. If they think it is not so urgent, then they don't have to make a fix -- but they know that the problem will be disclosed.

Nowhere in Google's documentation of this problem do I see a massive issue. Google gave MS 90 days. MS found a fix but there was another bug so they couldn't meet the window. Google released the information. Nowhere do I see MS requesting more time or any indication that anybody in the process thinks that anything went badly at all. It didn't meet the disclosure deadline. That's just the way it goes sometimes.

Re:Google discloses another Windows security issue after dea... by smt88 on Friday January 16, 2015 @03:54AM (#8897812)
You had one system on, at most, a few thousand machines, and those machines were tailored to the software.

The still-supported Windows versions, by contrast, are 50+ million lines of code EACH installed on hundreds of millions of machines EACH.

Your telephone switch analogy is just not even in the same solar system as what Microsoft is dealing with.

I'm not saying 90 days is necessarily too little time, I'm just saying your reasoning is totally flawed.

Re:Google discloses another Windows security issue after dea... by lern_too_spel on Thursday January 15, 2015 @11:17PM (#8897230)
The Kaminsky bug was disclosed 30 days after it was announced, and by then, pretty much the entire internet had been patched. Google is being generous with 90 days, and Microsoft is being utterly incompetent.
Re:Google discloses another Windows security issue after dea... by huhtenberg on Friday January 16, 2015 @04:16AM (#8897882)
This is trolling.
Re:Google discloses another Windows security issue after dea... by Malician on Friday January 16, 2015 @04:41PM (#8901912)
It's a reply to a poster who said,

"Imagine if Google found the Kaminsky DNS bug. The internet would have melted on day 91 when google told everyone, "Sorry, too bad."

Given this, if the Kaminsky bug was fixed in 31 days, that seems like a very bad example to use.

Re:Google discloses another Windows security issue after dea... by haneefmubarak on Friday January 16, 2015 @04:31AM (#8897939)
Then perhaps MS ought to shorten its bug fixing period. Three months is quite a long time to find a bug, fix it, and run extensive tests. What good is a fixed time period if you're willing to extend it just because one company can't pull their shit together?

As for the Kaminsky DNS bug, it was leaked more than a solid week ahead of the time he intended to release it. Sure, patches had already been released, but how about if other companies had said, "We need a full month to test this patch prior to rolling it into production."? They would have been putting themselves at risk. Mind you, this bug was simply an extension of an earlier flaw - too small a range of transaction IDs, and some DNS projects (`djbdns` comes to mind) had already mitigated it (ostensibly fixing the root cause as opposed to the symptom). Had the other vendors mitigated that flaw in a similar fashion (they had almost a decade since djb pointed it out), they would not have been vulnerable. However, there was no looming deadline, so few of them even noticed until an actual attack was possible (as opposed to fixing issues as they come up).

What happens if someone leaks the bug early? Or if a malicious adversary discovers the bug at the same time? The whole idea of these deadlines is to force security bug fixes to be released ASAP, taking precedence int time and importance over all else.

Deadlines can't be adjusted just so MS can screw around for longer doing nothing. If it's really taking them more than three months to fix a bug and release patches, perhaps they need to rethink their priorities and dedicate more resources to the task. And perhaps we need to seriously reconsider our dependence on their products.

Re:Google discloses another Windows security issue after dea... by gtirloni on Friday January 16, 2015 @05:22AM (#8898060)
Everybody is saying that 90 days is too much, even at MS' scale. So, taking into account that everybody seems to know very well what MS has to support, what is a good number of days to finish all the work that needs to be done?
Re:Google discloses another Windows security issue after dea... by haneefmubarak on Friday January 16, 2015 @06:17AM (#8898206)
90 days seems just fine. What they need to do is give greater importance to bugs and apply more resources accordingly.

When it actually affects them, they aren't hesitant to do whatever the hell it takes, with no regards as to the consequences for others, with zero warning at all, as was shown during the whole fiasco when they effectively took down NoIP's services. Meanwhile, when Google holds them to a perfectly reasonable deadline, for the extremely valid reason that bugs should be fixed on time, Google is evil?

Given their scale, they can afford to dedicate larger teams of people to the task of fixing security vulnerabilities. They can afford to hire independent security researchers and whatnot to help them find and fix such vulnerabilities.

If they need to break some third-party application in fixing a security vulnerability, that's okay. Because that application can also be fixed by its developer, and security needs come ahead of an app here or an app there. Besides, it isn't as if users of Microsoft's products are not used to the concept of having stuff break all the time anyways.

Have you noticed how quickly MS starts releasing patches and updates when a 0day comes out? That shows that they are clearly capable of doing whatever they need to do pretty damn quickly. They just don't do that with all security vulnerabilities, due to "business reasons", and as a result their customers suffer.

Re:Google discloses another Windows security issue after dea... by Amezarak on Friday January 16, 2015 @11:06AM (#8899717)
> If they need to break some third-party application in fixing a security vulnerability, that's okay. Because that application can also be fixed by its developer, and security needs come ahead of an app here or an app there.

That is exactly the opposite of what Microsoft's customers think. If Microsoft began taking this attitude, there would be mass outrage. And maybe rightfully so: for countless applications in the Windows world, the developers are no longer around or ask for money to update the software. People are more likely to simply not update or roll back the update after they get it.

> Besides, it isn't as if users of Microsoft's products are not used to the concept of having stuff break all the time anyways.

They actually aren't. It certainly happens, but it's very rare that a Windows update (or even upgrade) breaks anything.

Re:Google discloses another Windows security issue after dea... by boie0025 on Friday January 16, 2015 @12:19AM (#8897370)
In my experience, the only kind of PHP (or any) app where you can change just one line and walk away is a well written one. It's the poorly written ones where you have to change dozens or hundreds of lines, and run away screaming. But point taken.
Re:Google discloses another Windows security issue after dea... by danielweber on Friday January 16, 2015 @10:01AM (#8899246)
The issue isn't fixing the flaw. The issue is testing.

Say I patch a security flaw in a webapp I run. If I screw up the phone starts ringing, and then I undo the patch I made and think some more about it. Meanwhile no one has any clue about the flaw.

If I have to deploy a release to fixed endpoints, I have to think about what could possibly go wrong on every device out there running my software. Plus, if I didn't fix the problem completely, the nature of distributing the patch has now told the rev-eng community exactly where the problem was.

Google once pushed out a version of their browser that stopped the entire browser from working when their sync server went offline (for anyone using sync in their browser). Microsoft does not want even 1% of their users to suddenly be unable to use their computers.

Re:Google discloses another Windows security issue after dea... by RogerL on Friday January 16, 2015 @10:59AM (#8899670)
Ya, my comment was too brief. I was mostly reacting to the HN posters that basically were saying "Microsoft evil" by gently pointing out that other companies are leaving bugs in for longer than Microsoft. For example, someone posted "Other companies fix such bugs in days." Well, there are counterexamples, aren't there (OS X at the moment).

I think what Microsoft is doing is really hard. I don't have insight into their process, having never worked there. So yes, we can speculate that they could do things much faster. But can they? I find it rather tasteless to just assume so with no evidence and to then go on and call them names. I dunno, maybe they are falling flat on their faces internally, or maybe the team is performing heroics at the cost of personal lives, or maybe it is just business as usual.

But, it was also an honest question. Maybe there is evidence out there that Microsoft is just failing, and I haven't seen it or my reading comprehension failed me and I saw it but didn't register it.

But mostly, I am tired of the hurl accusations and drag people&companies through the mud meme that happens here, and this seemed to be more of the same (again, open to evidence, not claims, to the contrary).

Re:Google discloses another Windows security issue after dea... by bla2 on Friday January 16, 2015 @10:25AM (#8899411)
Another perspective is that Google found a bug through which they (and other businesses) can be owned, and ms is saying "fuck you" to google by not fixing it for months. Without this disclosure strategy, google wouldn't have any leverage to get bugs critical to their business (and to most other businesses) fixed. If your company is using windows, google is doing your company a favor.
Re:Google discloses another Windows security issue after dea... by username223 on Thursday January 15, 2015 @09:43PM (#8896988)
I think the issue is not the bug count, but that Microsoft tells Google "we will release a fix on day X," and Google says "X is past an arbitrary day we chose, so sad" and discloses a zero-day. Some people think it's an irresponsible PR stunt by Google, others that Microsoft would just put off fixes forever if Google didn't do this.

Maybe there's a similar story with OS X, but there doesn't seem to be a public record of it.

Re:Google discloses another Windows security issue after dea... by ahoge on Thursday January 15, 2015 @10:35PM (#8897125)
> [...] and discloses a zero-day.

90-day, you mean. It's only zero-day if they had zero days to come up with a solution. That's what "zero-day" means.

Re:Google discloses another Windows security issue after dea... by zabcik on Friday January 16, 2015 @02:15AM (#8897597)
But that doesn't sound nearly as cool or media hype-able.
Re:Google discloses another Windows security issue after dea... by username223 on Friday January 16, 2015 @02:33PM (#8901109)
I meant to say that there would be zero days between when I could patch my (hypothetical) Windows machine, and when people could start hacking it. The Wikipedia article you linked elsewhere seems ambiguous, e.g. "It is called a "zero-day" because the programmer has had zero days to fix the flaw (in other words, a patch is not available)." Microsoft has had something up to 90 days to produce such a patch, but hasn't for whatever reason.
[deleted]
Re:Google discloses another Windows security issue after dea... by ahoge on Friday January 16, 2015 @07:20AM (#8898386)
http://en.wikipedia.org/wiki/Zero-day_attack

> It is called a "zero-day" because the programmer has had zero days to fix the flaw

Re:Google discloses another Windows security issue after dea... by username223 on Monday January 19, 2015 @09:43PM (#8915200)
Did you read what you just linked? Specifically, the part after the open parenthesis? The bit about the patch not being available?

> It is called a "zero-day" because the programmer has had zero days to fix the flaw (in other words, a patch is not available).

Please try again.

Re:Google discloses another Windows security issue after dea... by Truff on Friday January 16, 2015 @07:18AM (#8898375)
Actually, 0-day refers to the time since public disclosure.
Re:Google discloses another Windows security issue after dea... by ahoge on Friday January 16, 2015 @07:29AM (#8898422)
If that would be the case then we would have another term for the thing I just described, because that's the worst case scenario.

Anyhow, the Wikipedia article disagrees with you, too. Got any sources for your definition?

Re:Google discloses another Windows security issue after dea... by Dylan16807 on Thursday January 15, 2015 @10:29PM (#8897107)
I really dislike your description because while it is technically true it heavily implies that they decided on dates on a per-bug case, when they decided on a flat 90 days.
Re:Google discloses another Windows security issue after dea... by erglkjahlkh on Friday January 16, 2015 @12:22AM (#8897376)
Then again, 90 days contains 2.5 of their fix cycles. If the vulnerability really is serious, and they can't fix it in that time line, they should exit the business.
Re:Google discloses another Windows security issue after dea... by josteink on Friday January 16, 2015 @04:21AM (#8897905)
Google roughly supports one version of their product on 2 OSs.

Microsoft supports all versions of all their products for 10years+ after release, integrated with a combination of all other products they have shipped in that same time-frame.

Needless to say, Microsoft needs to do more QA on their bug-fixes before they can safely release it to all customers without the risk of causing new issues.

It's easy for Google to be big in the mouth when they don't bother to support their existing customers properly.

Speaking of being big in the mouth: Did you know that Google isn't back-porting security fixes to older versions of Android either (only 2 last minor releases)? I guess supporting more than 40% of your user base is too much work.</sarcasm>

Guess which side my sympathy is leaning to in this case.

Re:Google discloses another Windows security issue after dea... by masklinn on Friday January 16, 2015 @05:37AM (#8898103)
> Needless to say, Microsoft needs to do more QA on their bug-fixes before they can safely release it to all customers without the risk of causing new issues.

IIRC Microsoft also releases pre-versions of their patches to select customers so sysadmins can test the patch doesn't cause issues on their deployments.

Re:Google discloses another Windows security issue after dea... by din-9 on Friday January 16, 2015 @01:04AM (#8897460)
As noted in the bug, it is not just writing a fix but writing one that works against all supported configurations that is the cause of a delay.
Re:Google discloses another Windows security issue after dea... by Kalium on Friday January 16, 2015 @02:04AM (#8897575)
> others that Microsoft would just put off fixes forever if Google didn't do this.

People wouldn't think that if MS didn't have a long history of doing exactly that.

Re:Google discloses another Windows security issue after dea... by throwawaykf05 on Friday January 16, 2015 @06:43AM (#8898271)
What security fixes has Microsoft put off forever?
Re:Google discloses another Windows security issue after dea... by MertsA on Friday January 16, 2015 @09:53AM (#8899192)
They are obviously much better about this now but back when IE was the browser du jour there were tons of bugs that took ages for them to fix.

http://blog.washingtonpost.com/securityfix/2007/01/critical_...

Re:Google discloses another Windows security issue after dea... by Kalium on Friday January 16, 2015 @01:26PM (#8900615)
Often they would dismiss a bug until someone exploited it to make a worm.
Re:Google discloses another Windows security issue after dea... by higherpurpose on Friday January 16, 2015 @12:14AM (#8897356)
No, I think the "issue" is that Apple doesn't talk to the media, while Microsoft immediately complained to some big tech sites about it, which then wrote the story from Microsoft's point of view.
Re:Google discloses another Windows security issue after dea... by duncan_bayne on Friday January 16, 2015 @04:17AM (#8897886)
"Some people think it's an irresponsible PR stunt by Google, others that Microsoft would just put off fixes forever if Google didn't do this."

... and yet others think that both of those statements are true :)

Re:Google discloses another Windows security issue after dea... by goalieca on Thursday January 15, 2015 @10:41PM (#8897137)
3 months is a long ass time to produce a patch.
Re:Google discloses another Windows security issue after dea... by aasarava on Thursday January 15, 2015 @10:54PM (#8897178)
Even if we're talking about such a massive roll-out to millions of machines, with various versions of the OS running on various hardware? I don't know how easy or not the actual patch is to produce, but it's not out of the realm of possibilities that they did run into a compatibility issue that they wanted more time to sort out. Think of the outcry and damage to their business if they rolled out a patch that accidentally broke some installations.
Re:Google discloses another Windows security issue after dea... by lern_too_spel on Thursday January 15, 2015 @11:12PM (#8897219)
Yes, even then. Imagine if the bug had been found by security researchers who believe in full disclosure. You think it's reasonable for Microsoft to allow dozens of rootkits and viruses to proliferate for more than three months, for botnets to grow to hundreds of millions in size? Microsoft's release process is broken.
Re:Google discloses another Windows security issue after dea... by tyree732 on Friday January 16, 2015 @02:22AM (#8897612)
Sure, three months is a long time to fix an issue, but what does Microsoft have to gain by taking longer to fix an issue of this severity than it believes it needs to? If Microsoft released the fixes when they were going to, and Google then released the details of the issues and when they first reported them, Google could still make a stink about Microsoft's turn-around time on critical security bugs, and there wouldn't be any gap between global notification of the issues and a readily available fix for them.

Put another way, Google may have just notified the world of black-hat hackers of an issue they weren't otherwise aware of, an issue that demonstrably will not be patched for some time. If that is the case, then Google just recklessly endangered people's computers in the interest of raising awareness of Microsoft's poor turn around time on these issues. There is also the very real chance that this issue was already known by the black-hat community, in which case there isn't nearly as much lost by reporting here, but that's a gamble Google is making in order to make a point.

Re:Google discloses another Windows security issue after dea... by throwawaykf05 on Friday January 16, 2015 @06:45AM (#8898278)
IIRC they do issue out-of-schedule patches if a vulnerability is severe enough and/or being actively exploited.
Re:Google discloses another Windows security issue after dea... by tedunangst on Friday January 16, 2015 @12:21AM (#8897372)
And if we're talking about a true 0-day being exploited in the wild? Microsoft is still unable to get a patch out in less than 90 days time? That's flat unacceptable. They need to be more responsive than that.
Re:Google discloses another Windows security issue after dea... by amaks on Friday January 16, 2015 @01:59AM (#8897561)
Think what you want, but IMO 90 days (even rounded to the nearest patch Tuesday) is plenty of time to fix the critical security issue. Clearly Microsoft is acting weird here.
Re:Google discloses another Windows security issue after dea... by nathanvanfleet on Thursday January 15, 2015 @09:10PM (#8896876)
Well HN needs links to be submitted, and then voted up. So I guess to answer your question is that no one at HN cared?
Re:Google discloses another Windows security issue after dea... by cheepin on Thursday January 15, 2015 @09:44PM (#8896992)
Yep, the collective "we" got what "we" wanted.