# CVE-2017-18228: Cross-site scripting in n/a

> Cross-site scripting in BMC Remedy AR System allows attackers to inject scripts via the ATTKey parameter, potentially leading to session hijacking or code execution.

- **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:** 12 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xpwq-6mfc-rr7g

## What is CVE-2017-18228?

CVE-2017-18228 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Mar 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

Remedy Mid Tier in BMC Remedy AR System 9.1 allows XSS via the ATTKey parameter in an arsys/servlet/AttachServlet request.

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

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

It affects 1 product.


Products: Bmc Remedy Action Request System.

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

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

## Is CVE-2017-18228 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18862](https://insights.sbomify.com/CVE-2018-18862/): Missing authorization in n/a (high 8.8)
- [CVE-2017-18223](https://insights.sbomify.com/CVE-2017-18223/): Auth bypass in n/a (high 8.1)
- [CVE-2016-2349](https://insights.sbomify.com/CVE-2016-2349/): Auth bypass in n/a (high 7.5)
- [CVE-2015-9257](https://insights.sbomify.com/CVE-2015-9257/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2007-0310](https://insights.sbomify.com/CVE-2007-0310/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18228 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Mar 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-18228 in the wild and no public exploit code.

Affected product: n/a. 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-18228/ (Markdown: https://insights.sbomify.com/CVE-2017-18228/index.md)
```

## Sources

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

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