CVE-2013-0598
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 · uneditedCross-site request forgery (CSRF) vulnerability in the Web Client in IBM Rational ClearQuest 7.1 before 7.1.2.12, 8.0 before 8.0.0.8, and 8.0.1 before 8.0.1.1 allows remote attackers to hijack the authentication of arbitrary users.
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 confidenceCross-site request forgery (CSRF) vulnerability in IBM Rational ClearQuest Web Client allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into unknowingly submitting malicious requests.
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.1.1.1= 7.1.1.2= 7.1.1.3= 7.1.1.4= 7.1.1.5= 7.1.1.6= 7.1.1.7= 7.1.1.8= 7.1.2= 7.1.2.1= 7.1.2.2= 7.1.2.3CVSS 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 ClearQuest installation and versionCheck the ClearQuest installation directory for a version file, or query the Windows registry under HKLM\SOFTWARE\IBM\Rational ClearQuest\CurrentVersion for the ProductVersion value. On Unix systems, check /opt/ibm/Rational/ClearQuest/Version or similar installation paths.Affected if The installed version matches 7.1.1.1, 7.1.1.2, 7.1.1.3, 7.1.1.4, 7.1.1.5, 7.1.1.6, 7.1.1.7, 7.1.1.8, 7.1.2, 7.1.2.1, 7.1.2.2, or 7.1.2.3 exactly.
-
Confirm Web Client component is activeVerify that the ClearQuest Web Client is deployed and accessible. Check if the cqweb application is running on your application server (WebSphere, Tomcat, or similar). Look for the cqweb URL endpoint responding to requests, typically at /cqweb/ or /clearquest/ paths.Affected if The Web Client interface is reachable and accepts authenticated user sessions.
-
Check for CSRF token validation in useInspect HTTP responses and form submissions in the ClearQuest Web Client. Submit a request and examine whether a CSRF token, security token, or session token is included in state-changing operations (POST requests that modify data).Affected if No CSRF token or anti-CSRF parameter is present in Web Client forms and AJAX requests.
-
Review web server logs for CSRF indicatorsExamine application server logs for suspicious cross-origin requests or patterns where external domains are triggering ClearQuest operations. Look for POST requests from unfamiliar referrer headers originating outside the trusted domain.Affected if Log analysis reveals unexpected cross-origin requests or potential CSRF exploitation attempts.
You are affected if ClearQuest version matches exactly 7.1.1.1 through 7.1.1.8, 7.1.2, 7.1.2.1, 7.1.2.2, or 7.1.2.3 AND the Web Client component is enabled and accessible to users.
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 vendor patches for versions 7.1.2.12, 8.0.0.8, 8.0.1.1 or later which include CSRF token validation. If patching is delayed, consider disabling the Web Client or implementing CSRF tokens at the web application firewall level.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0598 — 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-2013-0598 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