Security readout for executives and security teams
Plain-English summary
This vulnerability could let an outside attacker run code on a Jira Server or Jira Data Center system if they persuade an administrator to import a malicious workflow. It is high risk because successful exploitation can affect confidentiality, integrity, and availability, but it depends on administrator interaction.
Executive priority
Prioritize remediation for internet-facing or business-critical Jira environments. This is not described as actively exploited in the bundle, but the impact is full code execution if an administrator is deceived into importing a malicious workflow.
Technical view
Jira Server and Jira Data Center before 8.18.1 allowed unsafe OSWorkflow classes inside imported workflows through DefaultOSWorkflowConfigurator. The documented fix blocks unsafe OSWorkflow conditions, validators, functions, and registers from OSWorkflow and Jira dependencies. Atlassian-made functions and third-party plugin functions are described as unaffected.
Likely exposure
Exposure is likely limited to Jira Server or Jira Data Center instances below 8.18.1 where administrators can import workflows. The bundle does not provide a complete affected-version matrix beyond “before 8.18.1.”
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. Exploitation requires a remote attacker to trick a system administrator into importing a malicious workflow, so phishing or social engineering of Jira administrators is the key practical path.
Researcher notes
CVSS is 8.8 with network attack vector, no privileges required, and user interaction required. The evidence supports RCE through unsafe OSWorkflow classes in imported workflows. Do not assume exploitation without administrator import interaction or additional evidence.
Mitigation direction
- Upgrade Jira Server or Jira Data Center to 8.18.1 or later.
- Review Atlassian guidance for the exact fixed version path.
- Restrict workflow import rights to trusted Jira administrators only.
- Do not import workflows from untrusted sources.
- Review recently imported workflows for unexpected or unsafe workflow components.
Validation and detection
- Inventory Jira Server and Jira Data Center instances.
- Confirm each instance is version 8.18.1 or later.
- Identify who has permission to import workflows.
- Review workflow import history for untrusted sources.
- Check Atlassian JRASERVER-72660 for vendor-specific guidance.
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.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-18113 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-72660CVE reference · x_refsource_MISC
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.