# CVE-2007-4254: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the Visual Database Tools ActiveX control, requiring user interaction.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 8 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8hx5-8mhr-hxfm

## What is CVE-2007-4254?

CVE-2007-4254 is a medium-severity memory corruption vulnerability in Microsoft Visual Studio, published on 8 Aug 2007. 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

Stack-based buffer overflow in a certain ActiveX control in VDT70.DLL in Microsoft Visual Database Tools Database Designer 7.0 for Microsoft Visual Studio 6 allows remote attackers to execute arbitrary code via a long argument to the NotSafe method.  NOTE: this may overlap CVE-2007-2885 or CVE-2005-2127.

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

It affects 2 products.


Products: Microsoft Visual Database Tools Database Designer, Microsoft Visual Studio.

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

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

## Is CVE-2007-4254 being exploited?

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

Public exploit code:

- Microsoft Visual 6 - 'VDT70.dll NotSafe' Remote Stack Overflow (exploitdb)

## Other vulnerabilities in Microsoft Visual Studio

- [CVE-2007-2885](https://insights.sbomify.com/CVE-2007-2885/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4254 is a medium-severity memory corruption vulnerability in Microsoft Visual Studio, published on 8 Aug 2007. 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-2007-4254 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-2007-4254/ (Markdown: https://insights.sbomify.com/CVE-2007-4254/index.md)
```

## Sources

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

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