# CVE-2017-18097: Cross-site scripting in Jira

> Remote attackers can inject arbitrary HTML or JavaScript via Trello card titles, potentially leading to code execution or account takeover if an administrator imports the board.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c774-74r4-2fqx

## What is CVE-2017-18097?

CVE-2017-18097 is a medium-severity cross-site scripting vulnerability in Atlassian Jira, published on 6 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Trello board importer resource in Atlassian Jira before version 7.6.1 allows remote attackers who can convince a Jira administrator to import their Trello board to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the title of a Trello card.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Atlassian Jira.

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

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

## Is CVE-2017-18097 being exploited?

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

What it is: CVE-2017-18097 is a medium-severity cross-site scripting vulnerability in Atlassian Jira, published on 6 Apr 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-18097 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-18097/ (Markdown: https://insights.sbomify.com/CVE-2017-18097/index.md)
```

## Sources

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

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