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

> Remote attackers can execute arbitrary code via a buffer overflow in an ActiveX control, requiring user interaction to trigger.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5cqh-65ph-mxcx

## What is CVE-2007-2763?

CVE-2007-2763 is a critical memory corruption vulnerability in n/a, published on 18 May 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 UnlockSupport function in the LockModules subsystem in a certain ActiveX control in ltmm15.dll in Sienzo Digital Music Mentor (DMM) 2.6.0.4 allows remote attackers to execute arbitrary code via a long string in the second argument, a different issue than CVE-2007-2564.

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

It affects 1 product.


Products: Sienzo Digital Music Mentor.

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

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

## Is CVE-2007-2763 being exploited?

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

Public exploit code:

- LeadTools MultiMedia 15 - 'Ltmm15.dll' ActiveX Control Stack Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2564](https://insights.sbomify.com/CVE-2007-2564/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2763 is a critical memory corruption vulnerability in n/a, published on 18 May 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-2763 exists.

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

## Sources

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

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