dbcve.org
Mercury Quality CenterApplication · Hp

CVE-2007-1819

HIGH · 9.3 CVSS v2.0 Published 2007-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack-based buffer overflow in the SPIDERLib.Loader ActiveX control (Spider90.ocx) in Mercury Quality Center allows remote attackers to execute arbitrary code via a specially crafted long string to the ProgColor property.

MitigationApply vendor patches: Patch 12.1 for Quality Center 9.0 or Patch 32 for 8.2 SP1. Alternatively, disable the affected ActiveX control in Internet Explorer or implement network-level controls to restrict access to the vulnerable interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mercury Quality CenterApplication
Affected:= 8.2= 9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Mercury Quality Center is installed
    Look for the installation directory, typically in C:\Program Files\Mercury Quality Center or C:\Program Files\HP\Quality Center, or check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\Quality Center\CurrentVersion for the installed path and version.
    Affected if Quality Center version 8.2 or 9.0 is found installed on the system.
  2. Verify the exact installed version number
    Locate a version file or registry entry within the Quality Center installation directory or check the version info of the QC executable (tdlaunch.exe or similar) by right-clicking the file and selecting Properties.
    Affected if The installed version is exactly 8.2 or 9.0, as these are the affected versions.
  3. Confirm presence of the vulnerable ActiveX control
    Look for the file Spider90.ocx in the Quality Center installation directory (for example, C:\Program Files\Mercury Quality Center\bin\Spider90.ocx).
    Affected if The file Spider90.ocx exists in the Quality Center installation directory.
  4. Check if the ActiveX control is registered in Windows
    Check the Windows registry under HKEY_CLASSES_ROOT\CLSID for entries containing SPIDERLib.Loader or search for the CLSID corresponding to Spider90.ocx using reg query on HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib.
    Affected if The SPIDERLib.Loader ActiveX control is registered in the Windows registry and accessible to Internet Explorer.

A system is affected if Mercury Quality Center version 8.2 or 9.0 is installed AND the Spider90.ocx ActiveX control is present and registered on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches: Patch 12.1 for Quality Center 9.0 or Patch 32 for 8.2 SP1. Alternatively, disable the affected ActiveX control in Internet Explorer or implement network-level controls to restrict access to the vulnerable interface.

Recommended fix High confidence

Apply the vendor-supplied patches (Patch 12.1 for v9.0, Patch 32 for v8.2 SP1); for long-term resolution, migrate to a currently supported version of HP ALM (Application Lifecycle Management) which succeeded Quality Center

  1. 1. Identify the exact installed version of Mercury Quality Center / TestDirector by checking the About section in the application
  2. 2. For version 9.0: Apply Patch 12.1 or later from HP/Mercury's support website (webnotes.merc-int.com)
  3. 3. For version 8.2 SP1: Apply Patch 32 or later from HP/Mercury's support website
  4. 4. After applying the patch, verify the SPIDERLib.Loader ActiveX control (Spider90.ocx) has been updated and the ProgColor property is properly bounds-checked
  5. 5. Test that the Quality Center application functions normally after the patch
Caveat Standard patching risk - test in non-production environment first; patch may require application restart

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mercury Quality Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1819 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data