# CVE-2017-18113: Code injection in Jira Data Center

> Remote attackers can execute arbitrary code by tricking administrators into importing malicious workflows in Jira Server and Data Center.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Aug 2021
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-7q5w-8wg2-xwr7

## What is CVE-2017-18113?

CVE-2017-18113 is a high-severity code injection vulnerability in Atlassian Jira, published on 2 Aug 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The DefaultOSWorkflowConfigurator class in Jira Server and Jira Data Center before version 8.18.1 allows remote attackers who can trick a system administrator to import their malicious workflow to execute arbitrary code via a Remote Code Execution (RCE) vulnerability. The vulnerability allowed for various problematic OSWorkflow classes to be used as part of workflows. The fix for this issue blocks usage of unsafe conditions, validators, functions and registers that are build-in into OSWorkflow library and other Jira dependencies. Atlassian-made functions or functions provided by 3rd party plugins are not affected by this fix.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2017-18113?

It affects 2 products.


Products: Atlassian Data Center, Atlassian Jira.

## How do I fix CVE-2017-18113?

No fix has been published for CVE-2017-18113 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-18113 being exploited?

There is no known exploitation of CVE-2017-18113 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Jira

- [CVE-2021-41312](https://insights.sbomify.com/CVE-2021-41312/): Auth bypass in Jira Data Center (high 7.5)
- [CVE-2021-39123](https://insights.sbomify.com/CVE-2021-39123/): Denial of service in Jira Data Center (high 7.5)
- [CVE-2021-39113](https://insights.sbomify.com/CVE-2021-39113/): Missing authorization in Jira Data Center (high 7.5)
- [CVE-2021-43947](https://insights.sbomify.com/CVE-2021-43947/): Code injection in Jira Data Center (high 7.2)
- [CVE-2021-26070](https://insights.sbomify.com/CVE-2021-26070/): Auth bypass in Jira Data Center (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18113 and fix it if it is affected.

What it is: CVE-2017-18113 is a high-severity code injection vulnerability in Atlassian Jira, published on 2 Aug 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-18113 in the wild and no public exploit code.

Affected product: Atlassian Jira. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-18113/ (Markdown: https://insights.sbomify.com/CVE-2017-18113/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18113
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18113
- OSV: https://osv.dev/vulnerability/CVE-2017-18113

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-18113/
Summaries are generated and may contain mistakes; the official description above is the record.