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

> Remote attackers can trigger a buffer overflow in Microsoft Office ActiveX controls via a malicious web page, potentially executing arbitrary code.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 19 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c3jp-9rg8-8vx4

## What is CVE-2007-3282?

CVE-2007-3282 is a high-severity memory corruption vulnerability in Microsoft Office, published on 19 Jun 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

Buffer overflow in the Microsoft Office MSODataSourceControl ActiveX object allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long argument to the DeleteRecordSourceIfUnused method.

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

It affects 2 products.


Products: Microsoft Office, Microsoft Office Msodatasourcecontrol Activex.

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

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

## Is CVE-2007-3282 being exploited?

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

Public exploit code:

- Microsoft Office - MSODataSourceControl COM-object Buffer Overflow (PoC) (exploitdb)

## Other vulnerabilities in Microsoft Office

- [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3282 is a high-severity memory corruption vulnerability in Microsoft Office, published on 19 Jun 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-3282 exists.

Affected product: Microsoft Office. 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-3282/ (Markdown: https://insights.sbomify.com/CVE-2007-3282/index.md)
```

## Sources

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

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