Author Topic: Microsoft Security Advisory (927709)  (Read 2118 times)

Offline Caroline Lyons

  • Administrator
  • Member
  • *
  • Posts: 1411
    • CLICtech Internet & Computing Solutions
Microsoft Security Advisory (927709)
« on: December 12, 2006, 10:35:14 PM »
Microsoft Security Advisory (927709)
Vulnerability in Visual Studio 2005 Could Allow Remote Code Execution
Published: October 31, 2006 | Updated: December 12, 2006

Microsoft has completed the investigation into a public report of this vulnerability. We have issued MS06-073 to address this issue. For more information about this issue, including download links for an available security update, please review MS06-073. The vulnerability addressed is the Microsoft Visual Studio 2005 Vulnerability - CVE-2006-4704.


• You can provide feedback by completing the form by visiting the following Web site.
• Customers in the United States and Canada can receive technical support from Microsoft Product Support Services. For more information about available support options, see the Microsoft Help and Support Web site.
• International customers can receive support from their local Microsoft subsidiaries. For more information about how to contact Microsoft for international support issues, visit the International Support Web site.
• The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.


The information provided in this advisory 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.


• October 31, 2006: Advisory published.
• November 8, 2006: Advisory updated to alert customers that we are aware of attacks using the reported vulnerability.
• December 12, 2006: Advisory updated to reflect publication of security bulletin.
Freelance IT Journalist/Tech