CVE-2018-1394
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 · uneditedMultiple IBM Rational products are 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: 138425.
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 confidenceMultiple IBM Rational products contain a stored cross-site scripting (XSS) vulnerability in their Web UI. Attackers can embed arbitrary JavaScript code through user-supplied input, which executes within trusted sessions of other users, potentially exposing credentials or session tokens.
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>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.5>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.5>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.5>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.5>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.1>= 5.0.0, <= 5.0.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
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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 IBM Rational productLocate the installed IBM Rational application and note its name ( Doors Next Generation, Engineering Lifecycle Manager, Quality Manager, Rhapsody Design Manager, Software Architect Design Manager, or Team Concert). Check installed programs list, installation directory, or application startup splash screen.Affected if The product is any of the six affected IBM Rational products listed in the CVE.
-
Determine the installed product versionAccess the product's About or Version information panel within the application, or check the installation directory for version manifest files. Compare the version number against the affected ranges.Affected if The installed version falls within 5.0.0 through 5.0.2, or 6.0.0 through 6.0.5 (or 6.0.1 for Software Architect Design Manager).
-
Verify Web UI accessibilityConfirm the product's Web UI interface is enabled and accessible by navigating to the application's web URL (typically on port 9443 or similar). Attempt to log in to the web interface.Affected if The Web UI is accessible and user authentication is possible, as the XSS vulnerability requires user sessions in the web interface.
-
Check for user input fields in Web UILocate user-controllable input areas in the Web UI such as project names, descriptions, comments, or document fields where data can be submitted and stored.Affected if User-supplied input can be stored and displayed to other users within the web interface, which is the attack vector for this stored XSS.
You are affected if you run any of the six listed IBM Rational products and your installed version falls within 5.0.0-5.0.2 or 6.0.0-6.0.x and the Web UI is 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 dataImplement proper input validation and output encoding for all user-supplied data in the Web UI. Apply context-appropriate sanitization (HTML encoding, JavaScript escaping) and implement Content Security Policy headers to mitigate XSS execution.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1394 — 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-2018-1394 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