# CVE-2008-3704: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a long Mask parameter in the MaskedEdit ActiveX control, requiring user interaction to view malicious content.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 18 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x556-3584-m3v7

## What is CVE-2008-3704?

CVE-2008-3704 is a critical memory corruption vulnerability in Microsoft Visual Studio, published on 18 Aug 2008. 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

Heap-based buffer overflow in the MaskedEdit ActiveX control in Msmask32.ocx 6.0.81.69, and possibly other versions before 6.0.84.18, in Microsoft Visual Studio 6.0, Visual Basic 6.0, Visual Studio .NET 2002 SP1 and 2003 SP1, and Visual FoxPro 8.0 SP1 and 9.0 SP1 and SP2 allows remote attackers to execute arbitrary code via a long Mask parameter, related to not "validating property values with boundary checks," as exploited in the wild in August 2008, aka "Masked Edit Control Memory Corruption Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-3704?

It affects 4 products.


Products: Microsoft Visual Basic, Microsoft Visual Foxpro, Microsoft Visual Studio, Microsoft Visual Studio .Net.

## How do I fix CVE-2008-3704?

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

## Is CVE-2008-3704 being exploited?

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

Public exploit code:

- Microsoft Visual Studio Mdmask32.ocx ActiveX Stack Buffer Overflow (metasploit)
- Microsoft Visual Studio - 'Msmask32.ocx' ActiveX Remote Buffer Overflow (PoC) (exploitdb)
- Microsoft Visual Studio - 'Msmask32.ocx' ActiveX Remote Buffer Overflow (exploitdb)
- Microsoft Visual Studio - Msmask32.ocx ActiveX Buffer Overflow (MS08-070) (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Visual Studio

- [CVE-2006-4732](https://insights.sbomify.com/CVE-2006-4732/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-0392](https://insights.sbomify.com/CVE-2008-0392/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4776](https://insights.sbomify.com/CVE-2007-4776/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-2884](https://insights.sbomify.com/CVE-2007-2884/): Memory corruption in n/a (critical 9.3)
- [CVE-2001-0153](https://insights.sbomify.com/CVE-2001-0153/): Buffer overflow in VB-TSQL debugger object (vbsdicli.exe) in Visual Studio 6.0 Enterprise Edition allows remote attackers to execute arbitrary commands. (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3704 and fix it if it is affected.

What it is: CVE-2008-3704 is a critical memory corruption vulnerability in Microsoft Visual Studio, published on 18 Aug 2008. 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-2008-3704 exists.

Affected product: Microsoft Visual Studio. 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-2008-3704/ (Markdown: https://insights.sbomify.com/CVE-2008-3704/index.md)
```

## Sources

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

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