CVE-2005-2127 Memory corruption in n/a
Remote attackers can crash Internet Explorer or execute arbitrary code by tricking users into visiting a malicious web page with unsafe COM objects.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2005-2127?
CVE-2005-2127 is a high-severity memory corruption vulnerability in Microsoft .Net Framework, published on 19 Aug 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Microsoft Internet Explorer 5.01, 5.5, and 6 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a web page with embedded CLSIDs that reference certain COM objects that are not intended for use within Internet Explorer, as originally demonstrated using the (1) DDS Library Shape Control (Msdds.dll) COM object, and other objects including (2) Blnmgrps.dll, (3) Ciodm.dll, (4) Comsvcs.dll, (5) Danim.dll, (6) Htmlmarq.ocx, (7) Mdt2dd.dll (as demonstrated using a heap corruption attack with uninitialized memory), (8) Mdt2qd.dll, (9) Mpg4ds32.ax, (10) Msadds32.ax, (11) Msb1esen.dll, (12) Msb1fren.dll, (13) Msb1geen.dll, (14) Msdtctm.dll, (15) Mshtml.dll, (16) Msoeacct.dll, (17) Msosvfbr.dll, (18) Mswcrun.dll, (19) Netshell.dll, (20) Ole2disp.dll, (21) Outllib.dll, (22) Psisdecd.dll, (23) Qdvd.dll, (24) Repodbc.dll, (25) Shdocvw.dll, (26) Shell32.dll, (27) Soa.dll, (28) Srchui.dll, (29) Stobject.dll, (30) Vdt70.dll, (31) Vmhelper.dll, and (32) Wbemads.dll, aka a variant of the "COM Object Instantiation Memory Corruption vulnerability."
Weakness: CWE-119
Which versions are affected by CVE-2005-2127?
It affects 6 products.
Products include Ati Catalyst Driver, Microsoft .Net Framework, Microsoft Office, Microsoft Project, Microsoft Visio, Microsoft Visual Studio .Net.
How do I fix CVE-2005-2127?
No fix has been published for CVE-2005-2127 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2005-2127 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2127 exists.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in Microsoft .Net Framework
Sources
Also known as GHSA-hfcp-c62f-pjm6.