# CVE-2017-5983: Deserialization in n/a

> Remote attackers can execute arbitrary code, read files, or cause denial of service via crafted serialized Java objects in the JIRA Workflow Designer Plugin.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rr9q-89cr-8fcp

## What is CVE-2017-5983?

CVE-2017-5983 is a critical unsafe deserialization vulnerability in Atlassian Jira, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The JIRA Workflow Designer Plugin in Atlassian JIRA Server before 6.3.0 improperly uses an XML parser and deserializer, which allows remote attackers to execute arbitrary code, read arbitrary files, or cause a denial of service via a crafted serialized Java object.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Atlassian Jira.

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

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

## Is CVE-2017-5983 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-5983 exists.

Public exploit code:

- JIRA Workflow Designer Plugin in Atlassian JIRA Server > 6.3.0 - Remote Code Execution (XXE) (nuclei): http/cves/2017/CVE-2017-5983.yaml

## Other vulnerabilities in Atlassian Jira

- [CVE-2020-14172](https://insights.sbomify.com/CVE-2020-14172/): Deserialization in Jira Server (critical 9.8)
- [CVE-2019-20409](https://insights.sbomify.com/CVE-2019-20409/): Code injection in Jira Server (critical 9.8)
- [CVE-2010-1165](https://insights.sbomify.com/CVE-2010-1165/): Code injection in n/a (critical 9.0)
- [CVE-2016-4319](https://insights.sbomify.com/CVE-2016-4319/): Cross-site request forgery in Atlassian JIRA Server before 7.1.9 (high 8.8)
- [CVE-2019-8443](https://insights.sbomify.com/CVE-2019-8443/): Auth bypass in Jira (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5983 is a critical unsafe deserialization vulnerability in Atlassian Jira, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-5983 exists.

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-5983/ (Markdown: https://insights.sbomify.com/CVE-2017-5983/index.md)
```

## Sources

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

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