dbcve.org
Rational Engineering Lifecycle ManagerApplication · Ibm

CVE-2016-3014

MEDIUM · 5.4 CVSS v3.0 Published 2016-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Cross-site scripting (XSS) vulnerability in IBM Rational Collaborative Lifecycle Management 4.0 before 4.0.7 iFix11 and 5.0 before 5.0.2 iFix17, Rational Quality Manager 4.0 before 4.0.7 iFix11 and 5.0 before 5.0.2 iFix17, Rational Team Concert 4.0 before 4.0.7 iFix11 and 5.0 before 5.0.2 iFix17, Rational DOORS Next Generation 4.0 before 4.0.7 iFix11 and 5.0 before 5.0.2 iFix17, Rational Engineering Lifecycle Manager 4.x before 4.0.7 iFix11 and 5.0 before 5.0.2 iFix17, Rational Rhapsody Design Manager 4.0 before 4.0.7 iFix11 and 5.0 before 5.0.2 iFix17, and Rational Software Architect Design Manager 4.0 before 4.0.7 iFix11 and 5.0 before 5.0.2 iFix17 allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors.

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

Cross-site scripting (XSS) vulnerability in multiple IBM Rational lifecycle management products (CLM, RQM, RTC, DOORS Next Generation, RELM, Rhapsody Design Manager, RSA Design Manager) allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors. The vulnerability affects versions 4.0 before 4.0.7 iFix11 and 5.0 before 5.0.2 iFix17.

MitigationApply IBM Rational product updates to version 4.0.7 iFix11 or 5.0.2 iFix17 (or later) to remediate the XSS vulnerability. Validate that user inputs in the affected products are properly sanitized.

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:= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0.0= 5.0.1= 5.0.2
Rational Rhapsody Design ManagerApplication
Affected:= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0.0= 5.0.1= 5.0.2
Rational Quality ManagerApplication
Affected:= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0.0= 5.0.1= 5.0.2
Rational Software Architect Design ManagerApplication
Affected:= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0.0= 5.0.1= 5.0.2
Rational Doors Next GenerationApplication
Affected:= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0.0= 5.0.1= 5.0.2
Rational Team ConcertApplication
Affected:= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0.0= 5.0.1= 5.0.2
Rational Collaborative Lifecycle ManagementApplication
Affected:= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0.0= 5.0.1= 5.0.2

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/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 IBM Rational product
    Check the application name and version in the IBM Rational installation directory or via the product's About dialog (typically Help > About in the web interface)
    Affected if Any of these products are present: CLM, RQM, RTC, DOORS Next Generation, RELM, Rhapsody Design Manager, RSA Design Manager
  2. Determine the exact product version
    Access the product's admin or about page. For web-based Rational applications, navigate to https://<server>/<product>/admin/about or check the installation directory for version.info files
    Affected if Version is 4.0.0 through 4.0.7 (before iFix11), or 5.0.0 through 5.0.2 (before iFix17)
  3. Confirm authentication is enabled
    Verify the product requires user authentication to access. The vulnerability is exploitable by remote authenticated users, so the web interface must be accessible with valid credentials
    Affected if The product web interface is accessible and accepts user authentication (the XSS requires an authenticated session)
  4. Check if iFix level is identified
    Examine the installed iFix level by checking the product's fix history or About page which typically displays the full version string including iFix numbers (for example, 4.0.7 iFix010)
    Affected if The iFix number is below 11 for version 4.0.7, or below 17 for version 5.0.2 (or no iFix is installed)

A user is affected if they have any of the listed IBM Rational products running version 4.0.0-4.0.7 without iFix11 or version 5.0.0-5.0.2 without iFix17, where the web interface is accessible to authenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM Rational product updates to version 4.0.7 iFix11 or 5.0.2 iFix17 (or later) to remediate the XSS vulnerability. Validate that user inputs in the affected products are properly sanitized.

Fix this in Rational Engineering Lifecycle Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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