Jira ServerApplication · Atlassian
CVE-2017-18102
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 · uneditedThe wiki markup component of atlassian-renderer from version 8.0.0 before version 8.0.22 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in nested wiki markup.
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 confidenceA cross-site scripting (XSS) vulnerability exists in the wiki markup component of atlassian-renderer versions 8.0.0 through 8.0.21. The vulnerability allows remote attackers to inject arbitrary HTML or JavaScript via specially crafted nested wiki markup that is not properly sanitized during rendering.
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
Jira ServerApplication
>= 7.5.0, < 7.6.8>= 7.7.0, < 7.7.1>= 8.0.0, < 8.0.22CVSS 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.1/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 Jira Server versionAccess Jira administration or check the /rest/api/2/serverInfo endpoint, or look at the footer of any Jira page for the version numberAffected if The version falls within 7.5.0 to <7.6.8, or 7.7.0 to <7.7.1, or 8.0.0 to <8.0.22
-
Confirm atlassian-renderer component versionCheck the Jira installation directory for the atlassian-renderer jar file in the /opt/atlassian/jira/ atlassian-bundled-plugins/ or similar plugins directory, or inspect the WAR file if using a WAR deploymentAffected if The atlassian-renderer version is 8.0.0 through 8.0.21 (vulnerable range)
-
Verify wiki markup feature usageCheck if any Jira issues, confluence content (if integrated), or custom fields are using wiki markup rendering - search for content containing wiki markup syntax like {panel}, {anchor}, or nested markup constructsAffected if Wiki markup input is processed by the renderer without additional sanitization on output
-
Inspect application logs for XSS indicatorsReview Jira logs (atlassian-jira.log) for patterns involving script tags, javascript: URIs, or on*= event handlers within wiki markup fieldsAffected if Suspicious patterns appear in rendered wiki markup content
You are affected if your Jira Server version is 7.5.0-7.6.7, 7.7.0, or 8.0.0-8.0.21 and the wiki markup renderer is processing user-supplied input without additional sanitization.
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 data7.6.87.7.18.0.22
Upgrade atlassian-renderer to version 8.0.22 or later to obtain the vendor patch. If immediate patching is not possible, implement input validation and output encoding for all wiki markup input processed by the affected component.
Fix this in Jira Server
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18102 — 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-18102 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