# CVE-2005-1990: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code in Internet Explorer via malicious web pages referencing specific COM objects.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **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 available:** No
- **Published:** 10 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pgqj-26qf-9f3x

## What is CVE-2005-1990?

CVE-2005-1990 is a medium-severity memory corruption vulnerability in Microsoft Ie, published on 10 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

Internet Explorer 5.0, 5.5, and 6.0 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 ActiveX controls, including (1) devenum.dll, (2) diactfrm.dll, (3) wmm2filt.dll, (4) fsusd.dll, (5) dmdskmgr.dll, (6) browsewm.dll, (7) browseui.dll, (8) shell32.dll, (9) mshtml.dll, (10) inetcfg.dll, (11) infosoft.dll, (12) query.dll, (13) syncui.dll, (14) clbcatex.dll, (15) clbcatq.dll, (16) comsvcs.dll, and (17) msconf.dll, which causes memory corruption, aka "COM Object Instantiation Memory Corruption Vulnerability," a different vulnerability than CVE-2005-2087.

## Which versions are affected by CVE-2005-1990?

It affects 2 products.


Products: Microsoft Ie, Microsoft Internet Explorer.

## How do I fix CVE-2005-1990?

No fix has been published for CVE-2005-1990 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-1990 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1990 exists.

Public exploit code:

- Microsoft Internet Explorer - 'blnmgr.dll' COM Object Remote (MS05-038) (exploitdb)

## Other vulnerabilities in Microsoft Ie

- [CVE-2007-0217](https://insights.sbomify.com/CVE-2007-0217/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-0219](https://insights.sbomify.com/CVE-2007-0219/): Code injection in n/a (critical 10.0)
- [CVE-2006-1186](https://insights.sbomify.com/CVE-2006-1186/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0985](https://insights.sbomify.com/CVE-2004-0985/): Code injection in n/a (critical 10.0)
- [CVE-2004-0216](https://insights.sbomify.com/CVE-2004-0216/): Integer overflow in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1990 and fix it if it is affected.

What it is: CVE-2005-1990 is a medium-severity memory corruption vulnerability in Microsoft Ie, published on 10 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1990 exists.

Affected product: Microsoft Ie. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-1990/ (Markdown: https://insights.sbomify.com/CVE-2005-1990/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-1990
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-1990
- OSV: https://osv.dev/vulnerability/CVE-2005-1990

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-1990/
Summaries are generated and may contain mistakes; the official description above is the record.