dbcve.org
Rational Engineering Lifecycle ManagerApplication · Ibm

CVE-2018-1659

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: 144885.

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

Stored cross-site scripting (XSS) vulnerability in IBM Rational Engineering Lifecycle Manager (RELM) versions 5.0-5.02 and 6.0-6.0.6 allows authenticated users to embed arbitrary JavaScript code into the Web UI. This enables session hijacking and credential disclosure within trusted sessions.

MitigationApply IBM-provided patches for RELM versions 5.0.3+ and 6.0.1, or upgrade to fixed releases. Implement input validation and output encoding on user-supplied data in the Web interface as a defense-in-depth measure.

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 if IBM Rational Engineering Lifecycle Manager is installed
    Look for RELM processes running on the system (check task manager or running services for 'RELM', 'relm', or 'IBM Rational Engineering Lifecycle Manager' processes), or check for installation directories typically under IBM or Rational subfolders in Program Files on Windows or /opt on Linux/Unix.
    Affected if RELM software is found running or installed on the system
  2. Determine the installed RELM version
    Access the RELM Web UI and navigate to the About page (usually /relm/about or similar), or check for version files in the installation directory, or use the RELM command line tool if available (relmVersion.bat or similar).
    Affected if The installed version cannot be determined or is not documented
  3. Compare your version to the affected ranges
    Match your installed version against the affected ranges: 5.0 through 5.0.2 OR 6.0 through 6.0.6. Versions 5.0.3+ and 6.0.1+ contain fixes.
    Affected if The installed version falls within 5.0-5.0.2 or 6.0-6.0.6 inclusive
  4. Verify the Web UI is accessible
    Confirm the RELM Web interface is reachable by accessing the application URL (typically https://hostname:port/relm or http://hostname:port/relm). Check that the HTTP/HTTPS service is listening.
    Affected if The Web UI is not accessible or not configured (reduces exposure but version may still be vulnerable)
  5. Confirm authentication is enabled
    Verify that RELM user authentication is configured and active. Check that login is required to access the Web UI and that user accounts exist in the RELM user repository.
    Affected if Authentication is disabled (exploitation requires authenticated users to inject the XSS payload)

You are affected if IBM Rational Engineering Lifecycle Manager is installed with a version between 5.0-5.0.2 or 6.0-6.0.6 and the Web UI with authentication is enabled.

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

Apply IBM-provided patches for RELM versions 5.0.3+ and 6.0.1, or upgrade to fixed releases. Implement input validation and output encoding on user-supplied data in the Web interface as a defense-in-depth measure.

Fix this in Rational Engineering Lifecycle Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1659 — 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-1659 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