“Microsoft: Google had ongepatcht Windows-leak does not have to bring”

0
295

Microsoft is not happy that Google has released about a flaw in Windows 8.1 before Microsoft have a patch released to fix the problem. Microsoft comes Tuesday with a patch to fix the problem.

The researchers from Google discovered the vulnerability in late september, and gave Microsoft ninety days to address the vulnerability. Microsoft took that deadline is not, in which Google details about the vulnerability brought out.

Microsoft now says that it’s patch Tuesday will release, during its regular Patch Tuesday-beveiligingsronde. The company is, however, not happy that Google information about the leak to the outside has been brought before the patch is rolled out. “The decision of Google feel not generally, but more as a gotcha, in which consumers have suffered,” writes Chris Betz of the security department of Microsoft.

The company claims that security vulnerabilities only to the outside should be brought in if the problem is resolved. That would be users better protect against exploitation of the vulnerability. According to Google, set the deadline of ninety days companies under pressure to problems before to solve, which makes the impact of security vulnerabilities is reduced.

Microsoft writes that Google has asked to be ‘two days’ to wait with bringing out information about the vulnerability until the patch tuesday round. Google brought the information, however, already by the end of 2014 to the outside; probably referred to Microsoft two weeks in place of days.

The vulnerability ensures that a regular user on Windows 8.1 without permission administrator rights. Therefore, a user must have a valid login and physical access to the device. The problem was found by Project Zero, a security team from Google. Companies get ninety days of the time to find the vulnerabilities to be patched; after that, the team’s vulnerability to the outside.

Update, Tuesday, 12:30: May goes to a different vulnerability, points reader MIster X to. That bug was indeed two days for patch tuesday made public.