dbcve.org
Rational Quality ManagerApplication · Ibm

CVE-2016-0219

MEDIUM · 6.5 CVSS v3.0 Published 2018-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
XML external entity (XXE) vulnerability in IBM Rational Team Concert 3.0 before 3.0.1.6 iFix7 Interim Fix 1, 4.0 before 4.0.7 iFix10, 5.0 before 5.0.2 iFix15, and 6.0 before 6.0.1 iFix4 allows remote authenticated users to cause a denial of service via crafted XML data. IBM X-Force ID: 109693.

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

XML external entity (XXE) vulnerability in IBM Rational Team Concert allows remote authenticated users to cause denial of service via crafted XML data. The vulnerability affects versions 3.0.x before 3.0.1.6 iFix7, 4.0.x before 4.0.7 iFix10, 5.0.x before 5.0.2 iFix15, and 6.0.x before 6.0.1 iFix4.

MitigationApply the relevant IBM interim fixes (iFix7 for 3.0.x, iFix10 for 4.0.x, iFix15 for 5.0.x, iFix4 for 6.0.x) to disable external entity processing in the XML parser and prevent XXE-based DoS attacks.

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 Quality ManagerApplication
Affected:= 3.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= 4.0.0.1= 4.0.0.2= 4.0.1
Rational Requirements ComposerApplication
Affected:= 3.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= 4.0.1= 4.0.2= 4.0.3
Rational Doors Next GenerationApplication
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= 5.0.1= 5.0.2= 6.0
Rational Team ConcertApplication
Affected:= 3.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= 4.0.0.1= 4.0.0.2= 4.0.1
Rational Collaborative Lifecycle ManagementApplication
Affected:= 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= 4.0.1= 4.0.2= 4.0.3= 4.0.4
Rational Engineering Lifecycle ManagerApplication
Affected:= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.0= 6.0.1
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= 5.0.1= 5.0.2= 6.0
Rational Software Architect 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= 5.0.1= 5.0.2= 6.0

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 the installed IBM Rational product
    Check the application name and installed components in the IBM Jazz team server administration console or the installed programs list on the server
    Affected if The product is one of: Rational Team Concert, Rational Quality Manager, Rational Requirements Composer, Rational DOORS Next Generation, Collaborative Lifecycle Management, Rational Engineering Lifecycle Manager, Rational Rhapsody Design Manager, or Rational Software Architect Design Manager
  2. Determine the exact version number
    In the IBM Rational installation, look in the about section of the admin console, or check the installed.properties or version.info file in the installation directory
    Affected if A version is returned from the installation
  3. Compare version against affected ranges
    Match the installed version to these vulnerable ranges: 3.0.x before 3.0.1.6, 4.0.x before 4.0.7, 5.0.x before 5.0.2, or 6.0.x before 6.0.1
    Affected if The installed version falls within any of these ranges and does not have the corresponding iFix applied (iFix7 for 3.0.x, iFix10 for 4.0.x, iFix15 for 5.0.x, iFix4 for 6.0.x)
  4. Verify XML processing is active
    The application processes XML data by default for various features like requirements, test cases, or design artifacts. Check if the jazz server handles REST or SOAP API requests that accept XML payloads
    Affected if The application accepts XML input through its web services or API endpoints, which is the default behavior for these products

You are affected if you are running any of the listed IBM Rational products in versions 3.0.x before 3.0.1.6, 4.0.x before 4.0.7, 5.0.x before 5.0.2, or 6.0.x before 6.0.1 without the corresponding iFix applied.

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 the relevant IBM interim fixes (iFix7 for 3.0.x, iFix10 for 4.0.x, iFix15 for 5.0.x, iFix4 for 6.0.x) to disable external entity processing in the XML parser and prevent XXE-based DoS attacks.

Fix this in Rational Quality Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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