CVE-2024-28796
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 · uneditedIBM ClearQuest (CQ) 9.1 through 9.1.0.6 is vulnerable to stored cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 286833.
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 ClearQuest Web UI versions 9.1 through 9.1.0.6 is vulnerable to stored cross-site scripting, allowing authenticated users to embed arbitrary JavaScript code that executes in other users' browsers when viewing compromised content, potentially exposing session credentials.
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>= 9.1, < 9.1.0.7CVSS 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
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 the installed ClearQuest versionUse the ClearQuest version check mechanism (typically via cqversion command, or check the About section in the ClearQuest client or Web UI)Affected if The installed version is 9.1 through 9.1.0.6 (any version >= 9.1 but < 9.1.0.7)
-
Verify ClearQuest Web UI is accessibleAttempt to access the ClearQuest Web UI login page (typically at /cqweb/ or /clearquest/ on the application server)Affected if The Web UI is reachable and active in the environment
-
Confirm user authentication is enabledCheck that ClearQuest user authentication is configured and functional (users can log in through the Web UI)Affected if Users can authenticate to the ClearQuest Web UI, which enables the stored XSS attack vector
You are affected if your ClearQuest installation runs version 9.1 through 9.1.0.6 and the Web UI is accessible to authenticated 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.
dbcve · scoped9.1.0.7
Apply IBM's patch for this vulnerability and implement output encoding/input validation for all user-supplied content in the ClearQuest Web UI.
9.1.0.7
- 1. Download IBM Rational ClearQuest version 9.1.0.7 or later from IBM's official support portal (https://www.ibm.com/support)
- 2. Review IBM's official upgrade documentation and release notes for ClearQuest 9.1.0.7
- 3. Perform a complete backup of the ClearQuest database and all configuration files
- 4. Test the upgrade in a non-production environment before deploying to production
- 5. Run the ClearQuest 9.1.0.7 installer following IBM's standard upgrade procedures
- 6. Verify the upgrade was successful by checking the ClearQuest version in the About dialog
- 7. Confirm the stored XSS vulnerability is resolved by testing that JavaScript code cannot be embedded in Web UI fields
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-28796 — 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-2024-28796 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