CVE-2008-5329
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 · uneditedClearQuest Web in IBM Rational ClearQuest MultiSite before 7.1 allows remote servers to direct a client's submissions and changes to an arbitrary database by specifying multiple comma-separated server identifiers on the JTLRMIREGISTRYSERVERS line in a jtl.properties file.
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 confidenceIBM Rational ClearQuest MultiSite before version 7.1 contains a vulnerability in ClearQuest Web where remote servers can redirect client submissions and changes to an arbitrary database by specifying multiple comma-separated server identifiers in the JTLRMIREGISTRYSERVERS line of a jtl.properties configuration file. This allows an attacker to intercept or redirect data by controlling the server registry list.
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<= 7.0.0.3= 7.0.0.0= 7.0.0.1= 7.0.0.2= 7.0.1= 7.0.1.1= 7.0.1.2CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Determine installed ClearQuest versionCheck the ClearQuest application version through the About dialog in the ClearQuest client or by querying the installed packages. On Windows, this may be visible in Add/Remove Programs. On Unix, check the installation directory for version files.Affected if The installed version is 7.0.0.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.1, 7.0.1.1, or 7.0.1.2 (any version before 7.1).
-
Locate the jtl.properties configuration fileSearch for the file named jtl.properties in the ClearQuest Web configuration directory. This file is typically found in the ClearQuest Web server's configuration area, often under the web application deployment directory or in a shared configuration folder.Affected if The jtl.properties file exists and contains a JTLRMIREGISTRYSERVERS parameter.
-
Inspect the JTLRMIREGISTRYSERVERS parameterOpen the jtl.properties file and locate the line containing JTLRMIREGISTRYSERVERS. Examine the value assigned to this parameter.Affected if The parameter contains multiple comma-separated server identifiers (for example: server1,server2,server3) rather than a single trusted server.
-
Verify server registry list integrityReview each server identifier listed in the JTLRMIREGISTRYSERVERS line. Confirm that all listed servers are trusted, internal servers and that none point to unknown or external addresses.Affected if Any server identifier in the list points to an untrusted, unknown, or externally controlled server that you have not explicitly authorized.
You are affected if you are running any ClearQuest version before 7.1 AND your jtl.properties file contains a JTLRMIREGISTRYSERVERS line with multiple comma-separated server identifiers that include untrusted servers.
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 dataUpgrade to ClearQuest MultiSite 7.1 or later. Additionally, verify that jtl.properties files contain only trusted, validated server identifiers and consider implementing integrity checks on configuration files.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-5329 — 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-2008-5329 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