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

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the TestDirector ActiveX control, requiring user interaction to trigger.

- **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:** 2 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pxxg-mxf6-qpq5

## What is CVE-2007-1819?

CVE-2007-1819 is a critical memory corruption vulnerability in n/a, published on 2 Apr 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 the SPIDERLib.Loader ActiveX control (Spider90.ocx) 9.1.0.4353 in TestDirector (TD) for Mercury Quality Center 9.0 before Patch 12.1, and 8.2 SP1 before Patch 32, allows remote attackers to execute arbitrary code via a long ProgColor property.

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

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

It affects 1 product.


Products: Hp Mercury Quality Center.

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

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

## Is CVE-2007-1819 being exploited?

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

Public exploit code:

- HP Mercury Quality Center - Spider90.ocx ProgColor Overflow (exploitdb)
- HP Mercury Quality Center ActiveX Control ProgColor Buffer Overflow (metasploit)
- HP Mercury Quality Center - ActiveX Control ProgColor Buffer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5289](https://insights.sbomify.com/CVE-2007-5289/): Code injection in n/a (high 7.6)
- [CVE-2007-1882](https://insights.sbomify.com/CVE-2007-1882/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1819 is a critical memory corruption vulnerability in n/a, published on 2 Apr 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-1819 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-1819/ (Markdown: https://insights.sbomify.com/CVE-2007-1819/index.md)
```

## Sources

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

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