CVE-2018-1610
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 Rational DOORS Next Generation 5.0 through 5.0.2 and 6.0 through 6.0.6 are vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 143931.
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 DOORS Next Generation versions 5.0-5.0.2 and 6.0-6.0.6 contain a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code through user input fields, which executes in the browsers of other users viewing the same content, potentially exfiltrating session credentials or other sensitive data within a trusted session context.
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.6CVSS 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.
-
Identify installed DOORS Next Generation versionAccess the DOORS Next Generation administration console or check the installation directory for version information. Typically found in the installation path or via the 'About' menu in the Jazz team server admin interface.Affected if The installed version falls within 5.0-5.0.2 or 6.0-6.0.6.
-
Confirm Web UI is enabledVerify that the Web UI component is accessible by attempting to reach the DOORS Next Generation web interface through a browser. Check the Jazz Application (JTS) or DOORS Next Generation web URLs.Affected if The Web UI is accessible and users can interact with user input fields in the application.
-
Review recent artifacts or requirements for injected contentCheck recent artifacts, requirements, or modules that accept user-supplied text for any unexpected script tags, JavaScript event handlers, or encoded payloads. Use the DOORS Next Generation search or reporting features to query for patterns like '<script', 'javascript:', 'onerror=', or 'onload=' in text fields.Affected if Arbitrary script content is found stored in user-editable fields such as artifact text, comments, or module attributes.
-
Check audit logs for XSS attemptsExamine the DOORS Next Generation server logs and Jazz Team Server logs for suspicious requests containing XSS payloads in user input parameters. Look for patterns indicating injection attempts in web request parameters.Affected if Logs contain requests with script tags or JavaScript protocols in fields that accept user input.
A user is affected if they are running DOORS Next Generation versions 5.0 through 5.0.2 or 6.0 through 6.0.6 and the Web UI is accessible, with stored XSS payloads present in the database or evidence of injection attempts in logs.
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 dataImplement strict input validation and output encoding for all user-supplied data in the Web UI. Upgrade to a patched version if available from IBM. Apply IBM's published security patches for this vulnerability.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1610 — 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-2018-1610 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