CVE-2010-4600
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 · uneditedDojo Toolkit, as used in the Web client in IBM Rational ClearQuest 7.1.1.x before 7.1.1.4 and 7.1.2.x before 7.1.2.1, allows remote attackers to read cookies by navigating to a Dojo file, related to an "open direct" issue.
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 confidenceThe vulnerability allows remote attackers to read cookies by directly accessing Dojo Toolkit files in IBM Rational ClearQuest's web client. This 'open direct' issue enables cookie theft, potentially leading to session hijacking.
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 dataall versions= 7.1.1.1= 7.1.1.2= 7.1.1.3= 7.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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 IBM Rational ClearQuest installationCheck for ClearQuest installation directory and locate version information in registry (Windows) or in installation files (Linux/Unix). Common paths: Windows: C:\Program Files\IBM\Rational\ClearQuest, Linux: /opt/IBM Rational/ClearQuest. Look for a version file or use cq lsenv command.Affected if ClearQuest is not installed or version cannot be determined
-
Verify ClearQuest versionExecute 'cq lsenv' or check the About dialog in the ClearQuest client. On Windows, also check registry key HKLM\Software\IBM\Rational\ClearQuest\CurrentVersion. Extract the exact version number (e.g., 7.1.1.1, 7.1.1.2, 7.1.1.3, 7.1.2).Affected if Version matches 7.1.1.1, 7.1.1.2, 7.1.1.3, or 7.1.2 exactly
-
Confirm web client is enabledCheck if the ClearQuest Web server component is installed and running. Look for web server configuration files (cqweb.xml, plugin-cqweb.xml in application server config directories like WebSphere or Tomcat). Verify the web client URL is accessible.Affected if ClearQuest Web client is configured and accessible via browser
-
Check Dojo Toolkit file accessibilityAttempt to directly access Dojo Toolkit files in the web client directory. Typical path patterns: /cqweb/dojo/*, /cqweb/resource/dojo/*, or /clearquest/dojo/*. Use curl or browser to request paths like http://server:port/cqweb/dojo/src/debug.js and verify if files are served without authentication.Affected if Dojo Toolkit files are served directly without requiring authentication (the open direct condition)
A user is affected if running IBM Rational ClearQuest version 7.1.1.1, 7.1.1.2, 7.1.1.3, or 7.1.2 with the web client enabled and Dojo Toolkit files accessible without authentication.
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 IBM Rational ClearQuest to version 7.1.1.4 or 7.1.2.1 or later to patch the vulnerable Dojo Toolkit components.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4600 — 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-2010-4600 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