CVE-2005-2994
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 · uneditedUnspecified vulnerability in the web client for IBM Rational ClearQuest 2002.05.00 and 2002.05.20, and 2003.06.00 through 2003.06.15 before SR5, allows remote attackers to execute XML Style Sheets (XSS).
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 · moderate confidenceCross-site scripting (XSS) vulnerability in IBM Rational ClearQuest web client allows remote attackers to inject malicious script via XML Style Sheets. The vulnerability affects versions 2002.05.00, 2002.05.20, and 2003.06.00-2003.06.15 before Security Release 5.
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= 5.00= 5.20= 6.00= 6.10= 6.12= 6.13= 6.14= 6.15CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ClearQuest versionCheck the ClearQuest version through the client application (Help > About) or by querying the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rational ClearQuest\Version on Windows, or inspecting the installation directory for version information.Affected if The installed version matches 5.00, 5.20, 6.00, 6.10, 6.12, 6.13, 6.14, or 6.15, or corresponds to the 2002.05.00, 2002.05.20, or 2003.06.00-2003.06.15 release family.
-
Confirm web client is enabledDetermine if the ClearQuest web client interface is deployed and accessible. Check if the ClearQuest Web server component (typically IBM HTTP Server or WebSphere on port 80/443) is running and the web client URLs are reachable.Affected if The ClearQuest web client interface is actively accessible to users over the network.
-
Verify XML Style Sheet processing is activeConfirm that XML Style Sheet (XSL) transformation functionality is available through the web client. This is typically enabled by default in the web client for rendering queries and records.Affected if The web client can process and display data using XML Style Sheets, which is the default behavior in affected versions.
You are affected if you are running ClearQuest versions 5.00, 5.20, 6.00, 6.10, 6.12, 6.13, 6.14, or 6.15 (or the 2002.05/2003.06 release family) and the web client interface is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply ClearQuest SR5 patch or upgrade to a supported version. If running legacy systems, consider migrating to current supported versions as these older releases are likely end-of-life.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-2994 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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