# CVE-2017-18033: The Jira-importers-plugin in Atlassian Jira before version 7.6.1 allows remote attackers to create new projects and abort an executing exter


- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Jan 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-j5pf-67fx-vj74

## What is CVE-2017-18033?

CVE-2017-18033 is a medium-severity vulnerability in Atlassian Jira, published on 18 Jan 2018. 

### Official description

The Jira-importers-plugin in Atlassian Jira before version 7.6.1 allows remote attackers to create new projects and abort an executing external system import via various Cross-site request forgery (CSRF) vulnerabilities.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Atlassian Jira.

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

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

## Is CVE-2017-18033 being exploited?

There is no known exploitation of CVE-2017-18033 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-2017-18033 and fix it if it is affected.

What it is: CVE-2017-18033 is a medium-severity vulnerability in Atlassian Jira, published on 18 Jan 2018. 
Exploitation: There is no known exploitation of CVE-2017-18033 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-18033/ (Markdown: https://insights.sbomify.com/CVE-2017-18033/index.md)
```

## Sources

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

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