CVE-2007-0025: Code Injection

Published Feb 13, 2007
·
Updated

The MFC component in Microsoft Windows 2000 SP4, XP SP2, and 2003 SP1 and Visual Studio .NET 2000, 2002 SP1, 2003, and 2003 SP1 allows user-assisted remote attackers to execute arbitrary code via an RTF file with a malformed OLE object that triggers memory corruption. NOTE: this might be due to a stack-based buffer overflow in the AfxOleSetEditMenu function in MFC42u.dll.

Affected Software

6 affected components
Microsoft Visual Studio .NET=2003-gold
Microsoft Visual Studio .NET=2000-sp1
Microsoft Visual Studio .NET=2000
Microsoft Windows 2003 Server=2003-sp2
Microsoft Windows 2003 Server=xp_sp2
Microsoft Windows 2003 Server=2000-sp4

Event History

Feb 13, 2007
CVE Published
08:28 PM
Feb 14, 2007
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2007-0025?

CVE-2007-0025 is considered to have a high severity due to its potential to allow arbitrary code execution.

2

How do I fix CVE-2007-0025?

To fix CVE-2007-0025, ensure that your software is updated to the latest versions and apply relevant Microsoft security patches.

3

Which versions of software are affected by CVE-2007-0025?

CVE-2007-0025 affects Microsoft Windows 2000 SP4, XP SP2, 2003 SP1, and various versions of Visual Studio .NET.

4

What type of attack does CVE-2007-0025 enable?

CVE-2007-0025 enables user-assisted remote attackers to execute arbitrary code via a crafted RTF file.

5

How can I protect my systems from CVE-2007-0025?

To protect against CVE-2007-0025, avoid opening untrusted RTF files and keep your software updated with the latest security updates.

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