CVE-2019-4249
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 Rational Collaborative Lifecycle Management 6.0 through 6.0.6.1 is vulnerable to 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: 159647.
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 confidenceIBM Rational Collaborative Lifecycle Management versions 6.0 through 6.0.6.1 contains a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code that executes in the browsers of other users viewing the affected interface, potentially enabling credential theft through a trusted session.
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>= 6.0, <= 6.0.6.1>= 6.0, <= 6.0.6.1>= 6.0, <= 6.0.6.1>= 6.0, <= 6.0.6.1>= 6.0, <= 6.0.6.1>= 6.0, <= 6.0.1>= 6.0, <= 6.0.6.1CVSS 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 installed IBM Rational productCheck the application server or installed programs list for one of: Rational Collaborative Lifecycle Management, Rational DOORS Next Generation, Rational Engineering Lifecycle Manager, Rational Quality Manager, Rational Rhapsody Design Manager, Rational Software Architect Design Manager, or Rational Team ConcertAffected if Any of these products are installed
-
Check product version numberAccess the product's About or Version information page in the Web UI, or check the installation directory for a version file. Common locations include the admin console or the IBM Jazz team server administration interfaceAffected if Version is 6.0 through 6.0.6.1 (or 6.0.6.1 or earlier for Rational Software Architect Design Manager)
-
Confirm Web UI is enabledAttempt to access the Web UI login page at the standard Rational application URL (typically https://server:9443/rm, /ccm, /dm, or /qms depending on the product)Affected if The Web UI is accessible and responds
-
Verify the application is exposed on networkCheck network configuration to determine if the Web UI ports (default 9443, 8080, or 80) are exposed to untrusted networks or the internetAffected if The Web UI is externally accessible beyond trusted internal networks
The environment is affected if any of the listed IBM Rational products is installed with a version between 6.0 and 6.0.6.1 (or 6.0.6.1 or earlier for RSA Design Manager) and the Web UI is 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 dataUpgrade IBM Rational Collaborative Lifecycle Management to version 6.0.6.2 or later. As an interim measure, implement input validation and output encoding on user-supplied content, and consider deploying Content Security Policy headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4249 — 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-2019-4249 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