Security readout for executives and security teams
Plain-English summary
CVE-2017-18102 is a cross-site scripting flaw in Atlassian atlassian-renderer. A remote attacker could inject arbitrary HTML or JavaScript through nested wiki markup. Business impact depends on where this renderer is used, but exposed systems could put user sessions, page integrity, and trusted workflows at risk.
Executive priority
Prioritize remediation for internet-facing or broadly used systems that render user-generated wiki content. The issue is not KEV-listed and lacks published CVSS here, but remote XSS can affect trust, sessions, and user data.
Technical view
The wiki markup component of atlassian-renderer versions 8.0.0 before 8.0.22 mishandles nested wiki markup, allowing remote HTML or JavaScript injection. The source bundle does not provide CVSS, CWE, exploit details, or affected downstream product versions beyond the component.
Likely exposure
Exposure is likely where atlassian-renderer 8.0.0 through pre-8.0.22 is deployed or bundled and processes user-controlled wiki markup. The provided evidence names the renderer component, not a complete downstream product inventory.
Exploitation context
The sources describe remote XSS capability but do not show active exploitation. CVE data indicates the issue is not listed in KEV. Treat exploitation status as unconfirmed unless Atlassian or CISA later states otherwise.
Researcher notes
The key gap is mapping this component flaw to concrete deployments. Focus research on dependency presence, wiki markup input paths, and whether downstream Atlassian products or integrations bundle vulnerable atlassian-renderer versions.
Mitigation direction
- Inventory applications or plugins bundling atlassian-renderer.
- Upgrade atlassian-renderer to 8.0.22 or later where applicable.
- Review Atlassian guidance in JRASERVER-67108 and RNDR-153.
- Restrict untrusted wiki markup rendering until remediation is confirmed.
- Apply compensating content-security controls where supported.
Validation and detection
- Confirm deployed atlassian-renderer versions against the vulnerable range.
- Identify routes or features rendering user-supplied nested wiki markup.
- Review dependency lockfiles, build artifacts, and vendor bundles.
- Check Atlassian issue references for product-specific remediation notes.
- Verify post-upgrade rendering does not allow script execution.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-18102 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-67108CVE reference · x_refsource_CONFIRM
- https://jira.atlassian.com/browse/RNDR-153CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.