Security Advisory 2755801 Updated to Address Adobe Flash Player Issues documented in APSB13-08
Today we released an update that addresses vulnerabilities in Adobe Flash Player in Internet Explorer 10 on Windows 8. The details of the vulnerabilities are documented in Adobe security bulletin APSB13-08. The majority of customers have automatic updates enabled and will not need to take any action because the update will be downloaded and installed automatically. For those manually updating, we encourage you to read the advisory and apply this update as quickly as possible.
This update addresses the vulnerabilities in Adobe Flash Player by updating the affected Adobe Flash binaries contained within Internet Explorer 10. For more information, see the advisory.
— Wilson Guo, Program Manager, Internet Explorer
Comments
Anonymous
February 26, 2013
The comment has been removedAnonymous
February 26, 2013
Is the Win7 version affected by this? Will you release other performance/stability interim patches for IE10 down the road, such as something to fix the memory leak problem? Or will we have to wait 1-2 years again for a CHANCE for it to be fixed with IE11?Anonymous
February 26, 2013
The comment has been removedAnonymous
February 26, 2013
The comment has been removedAnonymous
February 27, 2013
@Arieta: Do you have a test case for your 'memory leak problem'? That is, can you point to a page that experiences what you consider to be a memory leak? Have you reduced that page to the minimum markup and script that still reproduces the problem? Engineers cannot fix problems that they cannot reproduce. They have a limited amount of time to fix bugs and if it's not possible to reproduce the bug easily, it's difficult to assess how serious the problem is and the priority for first reproducing, then fixing, the bug. As Internet Explorer 10 has now released, any bugs should be reported through Product Support Services. Go to support.microsoft.com for details. Note that if you got your copy of Windows preinstalled on your computer, you'll have to get support from the computer manufacturer rather than from Microsoft. I don't think this is a sensible approach either, but that is the way that the IE team have chosen to operate, so that's what you'll have to do.Anonymous
February 28, 2013
The comment has been removedAnonymous
March 01, 2013
6 commentAnonymous
March 01, 2013
6Anonymous
March 01, 2013
The comment has been removedAnonymous
March 03, 2013
The comment has been removedAnonymous
March 06, 2013
The comment has been removedAnonymous
March 10, 2013
The comment has been removed