Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Windows media files processing memory corruption

From:MICROSOFT <secure_(at)_microsoft.com>
Date:11.08.2009
Subject:Microsoft Security Bulletin MS09-038 - Critical Vulnerabilities in Windows Media File Processing Could Allow Remote Code Execution (971557)

Microsoft Security Bulletin MS09-038 - Critical
Vulnerabilities in Windows Media File Processing Could Allow Remote Code Execution (971557)
Published: August 11, 2009

Version: 1.0
General Information
Executive Summary

This security update resolves two privately reported vulnerabilities in Windows Media file processing. Either vulnerability could allow remote code execution if a user opened a specially crafted AVI file. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Critical for all supported editions of Microsoft Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by correcting the manner in which AVI headers are processed and correcting the manner in which AVI data is validated. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. None
Top of sectionTop of section
Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software
Operating System Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update

Microsoft Windows 2000 Service Pack 4


Remote Code Execution


Critical


None

Windows XP Service Pack 2 and Windows XP Service Pack 3


Remote Code Execution


Critical


None

Windows XP Professional x64 Edition Service Pack 2


Remote Code Execution


Critical


None

Windows Server 2003 Service Pack 2


Remote Code Execution


Critical


None

Windows Server 2003 x64 Edition Service Pack 2


Remote Code Execution


Critical


None

Windows Server 2003 with SP2 for Itanium-based Systems


Remote Code Execution


Critical


None

Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


Remote Code Execution


Critical


None

Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2


Remote Code Execution


Critical


None

Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*


Remote Code Execution


Critical


None

Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*


Remote Code Execution


Critical


None

Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2


Remote Code Execution


Critical


None

*Windows Server 2008 Server Core installation not affected. The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

Non-Affected Software
Operating System

Windows 7 for 32-bit Systems

Windows 7 for x64-based Systems

Windows Server 2008 R2 for x64-based Systems

Windows Server 2008 R2 for Itanium-based Systems
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.

I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Top of sectionTop of section
Vulnerability Information

Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the August bulletin summary. For more information, see Microsoft Exploitability Index.
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Malformed AVI Header Vulnerability - CVE-2009-1545 AVI Integer Overflow Vulnerability - CVE-2009-1546 Aggregate Severity Rating

Microsoft Windows 2000 Service Pack 4


Critical
Remote Code Execution


Critical
Remote Code Execution


Critical

Windows XP Service Pack 2 and Windows XP Service Pack 3


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows XP Professional x64 Edition Service Pack 2


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows Server 2003 Service Pack 2


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows Server 2003 x64 Edition Service Pack 2


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows Server 2003 with SP2 for Itanium-based Systems


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*


Critical
Remote Code Execution


Important
Denial of Service


Critical

Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2


Critical
Remote Code Execution


Important
Denial of Service


Critical

*Windows Server 2008 Server Core installation not affected. The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
Top of sectionTop of section

Malformed AVI Header Vulnerability - CVE-2009-1545

A remote code execution vulnerability exists in the way Microsoft Windows handles specially crafted AVI format files. This vulnerability could allow code execution if a user opened a specially crafted AVI file. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1545.

Mitigating Factors for Malformed AVI Header Vulnerability - CVE-2009-1545

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:


An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.


In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.


By default, all supported versions of Microsoft Outlook Express and Windows Mail open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to this issue through the Web-based attack scenario.
Top of sectionTop of section

Workarounds for Malformed AVI Header Vulnerability - CVE-2009-1545

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:


Deny access to Avifil32.dll

On Windows 2000, Windows XP, and Windows Server 2003 systems:

For 32bit Windows:

cacls %windir%\system32\avifil32.dll /E /P everyone:N

For 64bit Windows:

cacls %windir%\syswow64\avifil32.dll /E /P everyone

On Windows Vista and Windows Server 2008:

Run the following commands from a command prompt as an administrator:

For 32bit Windows:

icacls %windir%\system32 /restore %TEMP%\AVIFIL32_ACL.TXT

For 64bit Windows:

takeown /f %windir%\syswow64\avifil32.dll
icacls %windir%\syswow64\avifil32.dll /save %TEMP%\ AVIFIL32 _ACL.TXT
icacls %windir%\syswow64\avifil32.dll /deny everyone:(F)takeown /f

Impact of workaround: Applications that rely on the AVIFile API will fail to render AVI video content properly

How to undo the workaround:

On Windows 2000, Windows XP, and Windows Server 2003 systems:

For 32bit Windows:

cacls %windir%\system32\avifil32.dll /E /R everyone

For 64bit Windows:

cacls %windir%\syswow64\avifil32.dll /E /R everyone

On Windows Vista and Windows Server 2008:

Run the following commands from a command prompt as an administrator:

For 32bit Windows:

icacls %windir%\system32 /restore %TEMP%\AVIFIL32_ACL.TXT

For 64bit Windows:

icacls %windir%\syswow64 /restore %TEMP%\AVIFIL32_ACL.TXT



Remove HKEY_CLASSES_ROOT\CLSID\{40C3D757-D6E4-4b49-BB41-0E5BBEA28817}

Removing this registry will prevent Windows Explorer from previewing AVI files.

Using the Interactive Method

For 32-bit Windows systems:

1.Click Start, click Run, type Regedit in the Open box, and then click OK.

2.Locate the following subkey:
HKEY_CLASSES_ROOT\CLSID\{40C3D757-D6E4-4b49-BB41-0E5BBEA28817}

3.On the File menu, click Export.

4.In the Export Registry File dialog box, enter Video_Media_Properties_Handler_Backup.reg and click Save.

Note This will create a backup of this registry key in the My Documents folder by default.

5.Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

For 64-bit Windows systems:

1.Click Start, click Run, type Regedit in the Open box, and then click OK.

2.Locate the following subkey:
HKEY_CLASSES_ROOT\CLSID\{40C3D757-D6E4-4b49-BB41-0E5BBEA28817}

3.On the File menu, click Export.

4.In the Export Registry File dialog box, enter Video_Media_Properties_Handler_Backup1.reg and click Save.

Note This will create a backup of this registry key in the My Documents folder by default.

5.Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

6.Click Start, click Run, type Regedit in the Open box, and then click OK.

7.Locate the following subkey:
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{40C3D757-D6E4-4b49-BB41-
0E5BBEA28817}

8.On the File menu, click Export.

9.In the Export Registry File dialog box, enter  Video_Media_Properties_Handler_Backup2.reg and click Save.

Note This will create a backup of this registry key in the My Documents folder by default.

10.Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

Impact of workaround: Windows Explorer will not provide a preview image for AVI files.

Using a Managed Deployment Script

1.Create a backup copy of the registry keys by using a managed deployment script that contains the following commands:

For 32-bit Windows systems:
Regedit.exe /e Video_Media_Properties_Handler_Backup.reg
HKEY_CLASSES_ROOT\CLSID\{40C3D757-D6E4-4b49-BB41-0E5BBEA28817}

For 64-bit Windows Systems:
Regedit.exe /e Video_Media_Properties_Handler_Backup1.reg
HKEY_CLASSES_ROOT\CLSID\{40C3D757-D6E4-4b49-BB41-0E5BBEA28817}
Regedit.exe /e Video_Media_Properties_Handler_Backup2.reg
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{40C3D757-D6E4-4b49-BB41-
0E5BBEA28817}

2.Next, save the following to a file with a .REG extension, such as Disable_Video_Media_Properties_Handler.reg:

For 32-bit Windows systems:
Windows Registry Editor Version 5.00
[-HKEY_CLASSES_ROOT\CLSID\{40C3D757-D6E4-4b49-BB41-0E5BBEA28817}]

For 64-bit Windows Systems:
Windows Registry Editor Version 5.00
[-HKEY_CLASSES_ROOT\CLSID\{40C3D757-D6E4-4b49-BB41-0E5BBEA28817}]
[-HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{40C3D757-D6E4-4b49-BB41-
0E5BBEA28817}]

Run the above registry script on the target machine with the following command from an elevated command prompt:
Regedit.exe /s Disable_Video_Media_Properties_Handler.reg
Top of sectionTop of section

FAQ for Malformed AVI Header Vulnerability - CVE-2009-1545

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
The Windows component responsible for processing AVI files does not properly handle specially crafted AVI files with malformed headers.

What is an Audio Visual Interleave (AVI) file?
Audio Video Interleave (AVI) is a special case of Resource Interchange File Format (RIFF). The .avi file format is the most common container format for audio and video data on a computer. This file type is used with applications that capture, edit, and play back audio-video sequences. In general, AVI files contain multiple streams of different types of data. Most AVI sequences use both audio and video streams. A simple variation for an AVI sequence uses video data and does not require an audio stream.

Is Windows Media Player affected by this vulnerability?
No. The affected component is independent of the Windows Media Player version installed on the system.

What might an attacker use the vulnerability to do?
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability?
Exploitation of this vulnerability requires that a user open a specially crafted AVI file or receive specially crafted streaming content from a Web site or any application that delivers Web content.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a media file with a specially crafted AVI file embedded in it to the user and by convincing the user to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site that contains specially crafted content that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.

On Windows Vista and Windows Server 2008, an attacker could exploit the vulnerability by placing a specially crafted AVI file on a file system and convincing the user to navigate to the file’s location. On these platforms, Windows Explorer loads the affected DLL to provide a thumbnail and preview information for AVI files.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
The update addresses the vulnerability by correcting the manner in which AVI headers are processed.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Top of sectionTop of section
Top of sectionTop of section

AVI Integer Overflow Vulnerability - CVE-2009-1546

A remote code execution vulnerability exists in the way Microsoft Windows handles specially crafted AVI format files. This vulnerability could allow code execution if a user opened a specially crafted AVI file. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1546.

Mitigating Factors for AVI Integer Overflow Vulnerability - CVE-2009-1546

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:


An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.


In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.


By default, all supported versions of Microsoft Outlook Express and Windows Mail open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps mitigate attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to this issue through the Web-based attack scenario.
Top of sectionTop of section

Workarounds for AVI Integer Overflow Vulnerability - CVE-2009-1546

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:


Deny access to Avifil32.dll

On Windows 2000, Windows XP, and Windows Server 2003 systems:

For 32bit Windows:

cacls %windir%\system32\avifil32.dll /E /P everyone:N

For 64bit Windows:

cacls %windir%\syswow64\avifil32.dll /E /P everyone

On Windows Vista and Windows Server 2008:

Run the following commands from a command prompt as an administrator:

For 32bit Windows:

icacls %windir%\system32 /restore %TEMP%\AVIFIL32_ACL.TXT

For 64bit Windows:

takeown /f %windir%\syswow64\avifil32.dll
icacls %windir%\syswow64\avifil32.dll /save %TEMP%\ AVIFIL32 _ACL.TXT
icacls %windir%\syswow64\avifil32.dll /deny everyone:(F)takeown /f

Impact of workaround: Applications that rely on the AVIFile API will fail to render AVI video content properly

How to undo the workaround:

On Windows 2000, Windows XP, and Windows Server 2003 systems:

For 32bit Windows:

cacls %windir%\system32\avifil32.dll /E /R everyone

For 64bit Windows:

cacls %windir%\syswow64\avifil32.dll /E /R everyone

On Windows Vista and Windows Server 2008:

Run the following commands from a command prompt as an administrator:

For 32bit Windows:

icacls %windir%\system32 /restore %TEMP%\AVIFIL32_ACL.TXT

For 64bit Windows:

icacls %windir%\syswow64 /restore %TEMP%\AVIFIL32_ACL.TXT

Top of sectionTop of section

FAQ for AVI Integer Overflow Vulnerability - CVE-2009-1546

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
The Windows component for processing AVI files does not properly validate data within specially crafted AVI files.

What is an Audio Visual Interleave (AVI) file?
Audio Video Interleave (AVI) is a special case of Resource Interchange File Format (RIFF). The .avi file format is the most common container format for audio and video data on a computer. This file type is used with applications that capture, edit, and play back audio-video sequences. In general, AVI files contain multiple streams of different types of data. Most AVI sequences use both audio and video streams. A simple variation for an AVI sequence uses video data and does not require an audio stream.

Is Windows Media Player affected by this vulnerability?
No. The affected component is independent of the Windows Media Player version installed on the system.

What might an attacker use the vulnerability to do?
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability?
Exploitation of this vulnerability requires that a user open a specially crafted AVI file or receive specially crafted streaming content from a Web site or any application that delivers Web content.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a media file with a specially crafted AVI file embedded in it to the user and by convincing the user to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site that contains specially crafted content that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
The update addresses the vulnerability by correcting the manner in which AVI data is validated.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Other Information
Acknowledgments

Microsoft thanks the following for working with us to help protect customers:


Vinay Anantharaman of Adobe Systems, Inc. for reporting the Malformed AVI Header Vulnerability (CVE-2009-1545)


Vinay Anantharaman of Adobe Systems, Inc. for reporting the AVI Integer Overflow Vulnerability - (CVE-2009-1546)
Top of sectionTop of section
Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support


Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.


International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions


V1.0 (August 11, 2009): Bulletin published.

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod