CVE-2008-4255: Buffer Overflow

Published Dec 10, 2008
·
Updated

Heap-based buffer overflow in mscomct2.ocx (aka Windows Common ActiveX control or Microsoft Animation ActiveX control) in Microsoft Visual Basic 6.0, Visual Studio .NET 2002 SP1 and 2003 SP1, Visual FoxPro 8.0 SP1 and 9.0 SP1 and SP2, and Office Project 2003 SP3 and 2007 Gold and SP1 allows remote attackers to execute arbitrary code via an AVI file with a crafted stream length, which triggers an "allocation error" and memory corruption, aka "Windows Common AVI Parsing Overflow Vulnerability."

Affected Software

10 affected components
Microsoft Office FrontPage=2002-sp3
Microsoft Project=2003-sp3
Microsoft Project=2007
Microsoft Project=2007-sp1
Microsoft Visual Basic=6.0
Microsoft Visual FoxPro=8.0-sp1
Microsoft Visual FoxPro=9.0-sp1
Microsoft Visual FoxPro=9.0-sp2
Microsoft Visual Studio .NET=2002-sp1
Microsoft Visual Studio .NET=2003-sp1

Remediation

Event History

Dec 10, 2008
CVE Published
via MITRE·01:33 PM
Data Sourced
via MITRE·01:33 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2008-4255?

CVE-2008-4255 has a high severity rating due to the potential for remote code execution via exploited vulnerabilities in the affected ActiveX controls.

2

How do I fix CVE-2008-4255?

To fix CVE-2008-4255, users should apply the latest patches and updates provided by Microsoft for the affected software versions.

3

Which software is affected by CVE-2008-4255?

CVE-2008-4255 affects multiple Microsoft products including Visual Basic 6.0, Visual FoxPro 8.0 and 9.0, Visual Studio .NET 2002 and 2003, and several versions of Microsoft Project and Office FrontPage.

4

What are the risks of CVE-2008-4255 exploitation?

Exploitation of CVE-2008-4255 could allow attackers to execute arbitrary code on the host machine, potentially leading to unauthorized access and control.

5

Is there a workaround for CVE-2008-4255?

While the best course of action is to apply patches, users can mitigate risks by disabling ActiveX controls or limiting their use in untrusted environments.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203