dbcve.org
Rational Collaborative Lifecycle ManagementApplication · Ibm

CVE-2014-0862

HIGH · 10.0 CVSS v2.0 Published 2014-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Unspecified vulnerability in Jazz Team Server in IBM Rational Collaborative Lifecycle Management (CLM) 3.x before 3.0.1.6 iFix 2 and 4.x before 4.0.6 allows remote attackers to execute arbitrary code via unknown 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

Unspecified vulnerability in Jazz Team Server component of IBM Rational Collaborative Lifecycle Management (CLM) versions 3.x before 3.0.1.6 iFix 2 and 4.x before 4.0.6 allows remote unauthenticated attackers to execute arbitrary code via unknown vectors.

MitigationApply IBM Rational CLM patches 3.0.1.6 iFix 2 or later for 3.x versions, and 4.0.6 or later for 4.x versions. Restrict network exposure of Jazz Team Server interfaces until patching is complete.

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 Collaborative Lifecycle ManagementApplication
Affected:= 3.0.0= 3.0.1= 3.0.1.1= 3.0.1.2= 3.0.1.3= 3.0.1.4= 3.0.1.5= 3.0.1.6= 4.0.0= 4.0.1= 4.0.2= 4.0.3

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 CLM or Jazz Team Server is installed
    Check for CLM installation directories (typically under /opt/IBM or C:\Program Files\IBM) and look for jazz, clm, or Rational directories. Also check running processes for java.exe or websphere processes associated with CLM.
    Affected if IBM Rational CLM or Jazz Team Server software is found on the system
  2. Determine the installed CLM version
    Access the Jazz Team Server admin console (typically at https://server:9443/jazz/admin) and navigate to Server > About > View Installation Details. Alternatively, check the installation log files in the server/logs directory for version information.
    Affected if The installed version is 3.0.0, 3.0.1, 3.0.1.1, 3.0.1.2, 3.0.1.3, 3.0.1.4, 3.0.1.5, 3.0.1.6, 4.0.0, 4.0.1, 4.0.2, or 4.0.3
  3. Check if Jazz Team Server is network accessible
    Review firewall rules, network configuration, and reverse proxy settings to determine if the Jazz Team Server ports (default 9443 for HTTPS, 8080 for HTTP) are exposed to untrusted networks or the public internet.
    Affected if Jazz Team Server admin or web interfaces are reachable from untrusted network segments or the internet
  4. Verify the iFix level for version 3.0.1.6
    If running 3.0.1.6, check the installed iFixes via the IBM Installation Manager (Help > View Installed Packages) or by examining the /opt/IBM/IMShared directory for iFix metadata.
    Affected if Running 3.0.1.6 without iFix 2 installed

The environment is affected if IBM Rational CLM with Jazz Team Server is installed and the version is 3.0.0 through 3.0.1.6 without iFix 2, or version 4.0.0 through 4.0.3, and the server is network accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM Rational CLM patches 3.0.1.6 iFix 2 or later for 3.x versions, and 4.0.6 or later for 4.x versions. Restrict network exposure of Jazz Team Server interfaces until patching is complete.

Recommended fix High confidence

3.0.1.6 iFix 2 or later for CLM 3.x; 4.0.6 or later for CLM 4.x

  1. 1. Back up your current IBM Rational CLM installation and database before upgrading.
  2. 2. Review IBM Jazz Team Server upgrade documentation for your current version.
  3. 3. For CLM 3.x installations: Upgrade to version 3.0.1.6 iFix 2 or later.
  4. 4. For CLM 4.x installations: Upgrade to version 4.0.6 or later.
  5. 5. After upgrading, verify the Jazz Team Server is running and all services are operational.
  6. 6. Test critical CLM functions (requirements, development, quality management) to ensure the upgrade was successful.
Caveat IBM CLM upgrades may require database migration; review compatibility with existing integrations and custom plugins before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rational Collaborative Lifecycle Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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