dbcve.org
Rational Engineering Lifecycle ManagerApplication · Ibm

CVE-2018-1560

MEDIUM · 5.4 CVSS v3.0 Published 2018-09-25
Fix available
A fix is available. Upgrade to after 6.0.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
IBM Rational Engineering Lifecycle Manager 5.0 through 5.02 and 6.0 through 6.0.6 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: 142958.

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 confidence

IBM Rational Engineering Lifecycle Manager 5.0-5.02 and 6.0-6.0.6 contains a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code through user inputs that persists in the application, executing in browsers of other users viewing the affected content, potentially leading to credential disclosure via session hijacking within trusted sessions.

MitigationImplement robust input validation and output encoding/sanitization for all user-supplied data in the Web UI to prevent XSS execution.

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
Rational Engineering Lifecycle ManagerApplication
Affected:>= 5.0, <= 5.0.2>= 6.0, <= 6.0.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of IBM Rational Engineering Lifecycle Manager
    Check the product version through the Web UI by logging in and navigating to the About section, or by checking the installation directory for version metadata files such as version.ini or manifest files in the installation root.
    Affected if The installed version falls within 5.0 to 5.0.2 or 6.0 to 6.0.6 inclusive.
  2. Confirm Web UI is enabled and accessible
    Verify that the Rational Engineering Lifecycle Manager web interface is running and accessible by accessing the application URL (typically https://hostname:9443/rm or similar). Check if the login page loads successfully.
    Affected if The Web UI is accessible to users, which is the attack vector for this stored XSS vulnerability.
  3. Review user-controllable input fields in the application
    Log into the Web UI as a standard user and identify fields that accept user input and persist data, such as user profile fields, project descriptions, comments, or artifact metadata. These are potential injection points for stored XSS.
    Affected if User-supplied input is stored and displayed to other users without proper sanitization, enabling the stored XSS attack.
  4. Check for existing malicious scripts in stored data
    Examine application databases or stored artifacts for suspicious script tags or JavaScript code in text fields. Query the database for patterns like <script>, javascript:, or onload/onerror event handlers in user-created content.
    Affected if Arbitrary JavaScript code is found stored in user-editable fields that would execute when viewed by other users.
  5. Verify session management configuration
    Review the application configuration for session cookie settings, specifically HttpOnly and Secure flags on session cookies. Check if sessions can be hijacked via XSS due to missing protections.
    Affected if Session cookies lack HttpOnly flags, allowing JavaScript access to session tokens through XSS exploits.

A user is affected if they are running IBM Rational Engineering Lifecycle Manager versions 5.0-5.0.2 or 6.0-6.0.6 with the Web UI accessible and user input fields that persist data without proper sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 6.0.6
Interim mitigation

Implement robust input validation and output encoding/sanitization for all user-supplied data in the Web UI to prevent XSS execution.

Fix this in Rational Engineering Lifecycle Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1560 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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