Microsoft Chastises Google Over Chrome Security (pcmag.com)
An anonymous reader quotes PCMag:
In a Wednesday blog post, Redmond examined Google's browser security and took the opportunity to throw some shade at Chrome's security philosophy, while also touting the benefits of its own Edge browser. The post, written by Microsoft security team member Jordan Rabet, noted that Google's Chrome browser uses "sandboxing" and isolation techniques designed to contain any malicious code. Nevertheless, Microsoft still managed to find a security hole in Chrome that could be used to execute malicious code on the browser.
The bug involved a Javascript engine in Chrome. Microsoft notified Google about the problem, which was patched last month. The company even received a $7,500 reward for finding the flaw. However, Microsoft made sure to point out that its own Edge browser was protected from the same kind of security threat. It also criticized Google for the way it handled the patching process. Prior to the patch's official rollout, the source code for the fix was made public on GitHub, a software collaboration site that hosts computer code. That meant attentive hackers could have learned about the vulnerability before the patch was pushed out to customers, Microsoft claimed. "In this specific case, the stable channel of Chrome remained vulnerable for nearly a month," the blog post said. "That is more than enough time for an attacker to exploit it."
In the past Google has also disclosed vulnerabilities found in Microsoft products -- including Edge.
The bug involved a Javascript engine in Chrome. Microsoft notified Google about the problem, which was patched last month. The company even received a $7,500 reward for finding the flaw. However, Microsoft made sure to point out that its own Edge browser was protected from the same kind of security threat. It also criticized Google for the way it handled the patching process. Prior to the patch's official rollout, the source code for the fix was made public on GitHub, a software collaboration site that hosts computer code. That meant attentive hackers could have learned about the vulnerability before the patch was pushed out to customers, Microsoft claimed. "In this specific case, the stable channel of Chrome remained vulnerable for nearly a month," the blog post said. "That is more than enough time for an attacker to exploit it."
In the past Google has also disclosed vulnerabilities found in Microsoft products -- including Edge.
Do we point out Microsoft's long and illustrious history of ignoring critical security flaws now or...
Do we just point out Chrome isn't crashing computers with their security updates, thus training their users to turn off automatic updates?
I know, I know, its not the same thing exactly. But you know what they say about people in glass houses.
Good has some really good programmers, and so does Microsoft. In the past they were even more impressive.
But both of them are now process driven companies, primarily focused on not overturning the boat, and the result is code that follows process. As long as process is followed, you don't have to worry about whether you did a good job or not. Just go home at the end of the day. That is the mentality of the vast majority of mediocre programmers at both companies.
"First they came for the slanderers and i said nothing."
Says it has poor cleanliness standards.
Local high school basketball coach criticizes NFL team for its poor tackling form on Sunday.
While I agree with them, it should be noted that Edge is not even in the same league as Chrome.
Bugs happen. What has me worried is a month long waiting time between security fix in public facing repository and release. This pretty much asks for exploitation even by not very skilled "hackers" as interested parties have lots of time to prepare viable exploit based on provided regression tests.
I don't know of any other company that has a monthly release cycle for security updates, even for zero day bugs! Google you are evil, you should be like Micros... oh.
People who live in glass houses...
...Trying to outdo each other at finding browser vulnerabilities. Outcome : both browser become more secure.
C. Sagan : A demon haunted world:
http://www.amazon.com/gp/product/0345409469/
visit randi.org
I mean.. seriously?
I don't read AC
Well this was covered recently
Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
In a professional setting, updates are tested on a test server to make sure they don't break anything before they are applied to production servers. And the moment they are applied is planned carefully. Auto update is irrelevant there, what is relevant is that Euqifax didn't handle their environment like a professional should.
I wrote about this:
http://robert.ocallahan.org/20...
Summary: In practice, attackers can leverage arbitrary-write bugs to produce the same-origin violations Microsoft warns about without requiring RCE, completely bypassing the CFI mitigations Microsoft is touting here.
Microsoft desperately needs money. They are left to find bugs in Chrome to get the $1,000 award
Slashdot, fix the reply notifications... You won't get away with it...
"we set out to examine Google’s Chrome web browser .. is having a strong sandboxing model sufficient to make a browser secure?" Jordan Rabet Microsoft Offensive Security Research team
That's a bit rich coming from Microsoft. Security resides in the Operating not in the Browser. Chrome wouldn't need sandboxing if the underlying Operating System did its job. That is isolate one processes memory from the other. Something the WinTEL platform seem unable to do despite numerous iterations of the x86 processor.
I love how the original "research" article tried to spin defects in the underlying Operating System into, it's somehow the fault of sandboxing in Chrome. Sandboxing, OSR, RCE, CFG, ACG, LPAC, WDAG, all designed to protect the underlying Operating System from the browser. Microsoft, the company that fights malware with self-serving adverts masquerading as technical research.
Anonymous Coward: 'Was demonstrated once more by the Equifax mega breach.'
The Equifax mega breach demonstrated what happens when a company with an annual turnover of US$ 3.1 billion, uses software on an Internet facing machine without testing it for security vulnerabilities. In fact they didn't even have a patch strategy in place or even know who was responsible for implementing such patches.
*Bill Maher enters the stage, waits for cheering to calm down*
Bill - "Good evening ladies and gentlemen, as we've just heard from the tech community, ..."
Microsoft Chastises Google over Security
*laughter errupts* ...
We suffer more in our imagination than in reality. - Seneca
That sounds reasonable but tend to not work out for non-trivial systems. It's better to always update, even in production, and detect failures and mitigate them.
You've had experience mitigating boot failures on 50,000 PCs, while every minute of downtime is costing the company many thousands of dollars?
If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
We found something that's insecure in Chrome that Edge isn't susceptible to!
Hey, that's reason to celebrate, and use the good champagne. It's not like it happens often.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
...as easily as I do in Chrome?
No?
Then fuck off with that.
"Oh my God. This is terrible. This is the end of my Presidency. I'm fucked."; ~ Donald J. Trump
That sounds reasonable but tend to not work out for non-trivial systems. It's better to always update, even in production, and detect failures and mitigate them.
You've had experience mitigating boot failures on 50,000 PCs, while every minute of downtime is costing the company many thousands of dollars?
No, because I release/stage updates to a small pilot group first the first night(s) and only roll them out to the masses if the pilot group(s) have no issues or only when those issues are resolved.
I suppose your "ignore problems and then blame any/everyone else" for not properly managing your infrastructure style works for you too.
Ahh... not auto-updates, then.
I'm guessing it's Nadella's changes.
Don't want to be tough on Ballmer, but that's a fact.
Slashdot, fix the reply notifications... You won't get away with it...
"He who is without sin cast the first .... something or other"
READY.
PRINT ""+-0
It does seem like he is claiming both side of that issue.
If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
... yeah, that's what I thought. They can't fully secure a browser on 1 platform but they're going to call out a browser that runs on no less than 5 platforms? Amateurs.
https://www.cvedetails.com/vul...
Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
Unless you are a teenager, please don't use the slang "throwing shade". It just makes you sound like a old person, desperately trying to appear cool by talking like a teenager.
This article brings me the first laugh of this day. Ironic, Don't you think?
Automated updates does not mean that every single host applies the update at the same time though.
If you are testing on a subset, then deciding whether or not these then are applied to a wider set of machines, I am hard pressed to see how that is an auto-update and not a traditional test and release methodology.