CVE-2017-1329
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 · uneditedIBM Quality Manager (RQM) 5.0.x and 6.0 through 6.0.5 are vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site. IBM X-Force ID: 126231.
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 confidenceIBM Rational Quality Manager (RQM) versions 5.0.x and 6.0-6.0.5 contain an HTML injection vulnerability that allows remote attackers to inject malicious HTML code into web pages served by the application. When authenticated users view the injected content, it executes within the security context of the hosting site, potentially leading to session hijacking, cookie theft, or further 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>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 5.0.0, <= 6.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate IBM Rational Quality Manager installationSearch for RQM installation directories (common paths: /opt/IBM/jazz or C:\Program Files\IBM\jazz) or identify running Jazz Team Server processes that host RQM applicationsAffected if RQM or CLM software is present on the system but version cannot be verified or falls within affected ranges
-
Determine installed RQM versionAccess the RQM admin console or check the version file in the installation directory (look for version.info or similar), or query the /qm/service/version REST endpoint if the web interface is accessibleAffected if Version is 5.0 through 5.0.2, or 6.0 through 6.0.5 (the exact version string will confirm the range)
-
Check IBM Rational CLM version if installedIf Rational Collaborative Lifecycle Management is deployed separately, check its version through the CLM admin interface or installation metadataAffected if Version is 5.0.0 through 6.0.3 inclusive
-
Confirm web interface accessibilityVerify if the RQM or CLM web application is exposed by checking for running IBM HTTP Server or WebSphere Liberty/traditional profiles serving the applicationAffected if The web interface is accessible over the network and the application version is within the affected ranges listed above
The environment is affected if IBM Rational Quality Manager version 5.0-5.0.2 or 6.0-6.0.5, or IBM Rational Collaborative Lifecycle Management version 5.0.0-6.0.3 is confirmed as installed and accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply IBM's official patch for this vulnerability (RQM 6.0.6 or later, or equivalent patched 5.0.x version). Implement output encoding and input validation as compensating controls until the patch can be deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1329 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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