# CVE-2007-0468: Stack-based buffer overflow in rcdll.dll in msdev.exe in Visual C++ (MSVC) in Microsoft Visual Studio 6.0 SP6 allows user-assisted remote at


- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hchh-2854-2rp2

## What is CVE-2007-0468?

CVE-2007-0468 is a medium-severity vulnerability in Microsoft Visual Studio, published on 24 Jan 2007. 

### Official description

Stack-based buffer overflow in rcdll.dll in msdev.exe in Visual C++ (MSVC) in Microsoft Visual Studio 6.0 SP6 allows user-assisted remote attackers to execute arbitrary code via a long file path in the "1 TYPELIB MOVEABLE PURE" option in an RC file.

## Which versions are affected by CVE-2007-0468?

It affects 1 product.


Products: Microsoft Visual Studio.

## How do I fix CVE-2007-0468?

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

## Is CVE-2007-0468 being exploited?

There is no known exploitation of CVE-2007-0468 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Visual Studio

- [CVE-2025-49739](https://insights.sbomify.com/CVE-2025-49739/): Visual Studio Elevation of Privilege Vulnerability (high 8.8)
- [CVE-2022-35777](https://insights.sbomify.com/CVE-2022-35777/): Visual Studio Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-35825](https://insights.sbomify.com/CVE-2022-35825/): Visual Studio Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-35826](https://insights.sbomify.com/CVE-2022-35826/): Visual Studio Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-35827](https://insights.sbomify.com/CVE-2022-35827/): Visual Studio Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0468 and fix it if it is affected.

What it is: CVE-2007-0468 is a medium-severity vulnerability in Microsoft Visual Studio, published on 24 Jan 2007. 
Exploitation: There is no known exploitation of CVE-2007-0468 in the wild and no public exploit code.

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-2007-0468/ (Markdown: https://insights.sbomify.com/CVE-2007-0468/index.md)
```

## Sources

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

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