# CVE-2019-15013: Missing authorization in Jira

> Authenticated attackers without admin rights can remove issue statuses from projects due to missing authorization checks in Jira.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hmpw-22jw-wcrr

## What is CVE-2019-15013?

CVE-2019-15013 is a medium-severity missing authorization vulnerability in Atlassian Jira, published on 18 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WorkflowResource class removeStatus method in Jira before version 7.13.12, from version 8.0.0 before version 8.4.3, and from version 8.5.0 before version 8.5.2 allows authenticated remote attackers who do not have project administration access to remove a configured issue status from a project via a missing authorisation check.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2019-15013?

It affects 2 products.


Products: Atlassian Jira, Atlassian Jira Server.

## How do I fix CVE-2019-15013?

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

## Is CVE-2019-15013 being exploited?

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

## 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-2017-5983](https://insights.sbomify.com/CVE-2017-5983/): Deserialization in n/a (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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15013 and fix it if it is affected.

What it is: CVE-2019-15013 is a medium-severity missing authorization vulnerability in Atlassian Jira, published on 18 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15013 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-2019-15013/ (Markdown: https://insights.sbomify.com/CVE-2019-15013/index.md)
```

## Sources

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

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