CVE-2017-1700
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 Jazz Team Server affecting the following IBM Rational Products: Collaborative Lifecycle Management (CLM), Rational DOORS Next Generation (RDNG), Rational Engineering Lifecycle Manager (RELM), Rational Team Concert (RTC), Rational Quality Manager (RQM), Rational Rhapsody Design Manager (Rhapsody DM), and Rational Software Architect (RSA DM) could allow an authenticated user to cause a denial of service due to incorrect authorization for resource intensive scenarios. IBM X-Force ID: 134392.
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 · moderate confidenceIBM Jazz Team Server contains an incorrect authorization check that allows authenticated users to trigger resource-intensive operations, potentially causing denial of service. An authenticated attacker can exploit this flaw by sending specially crafted requests that consume excessive server resources.
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, <= 6.0.5>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 5.0, <= 5.0.2>= 6.0, <= 6.0.1>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the IBM Rational productCheck which IBM Rational application is running on your Jazz Team Server. This can be done via the Jazz administrative console at https://<server>/jts/admin, or by checking the installed applications list in the Jazz Hub.Affected if The product is one of: Rational Collaborative Lifecycle Management, Rational Doors Next Generation, Rational Engineering Lifecycle Manager, Rational Quality Manager, Rational Rhapsody Design Manager, Rational Software Architect Design Manager, or Rational Team Concert.
-
Determine the product versionAccess the About section in the Jazz web UI (typically via the help menu or /jts/about), or check the version information in the installation directory's about.html file. For command-line, check the installation directory for a version.info or similar version file.Affected if The installed version falls within the affected ranges: >5.0 to <=6.0.5 for CLM; 5.0 to 5.0.2 or 6.0 to 6.0.5 for most products; or 6.0 to 6.0.1 for Rational Software Architect Design Manager.
-
Confirm Jazz Team Server component versionThe vulnerability exists in the Jazz Team Server component. Check the Jazz Team Server version by accessing https://<server>/jts/admin and viewing the server information, or by examining the jts.war or server version details in the installation.Affected if The Jazz Team Server version matches the same affected version ranges as the Rational products.
-
Verify user authentication is enabledCheck the Jazz Team Server security configuration at https://<server>/jts/admin#security to confirm that user authentication (Jazz Authorization Server) is configured and active.Affected if Authentication is enabled and users can log in, which is required for this vulnerability to be exploitable.
Your environment is affected if you are running any of the listed IBM Rational products (or Jazz Team Server) within versions 5.0.x through 6.0.5 (or 6.0.1 for RSA Design Manager) with user authentication enabled.
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 the appropriate IBM Jazz Team Server patches or updates for all affected Rational products. Review and enforce proper authorization policies for resource-intensive operations in the Jazz platform configuration.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1700 — 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-1700 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