# CVE-2017-16022: Cross-Site Scripting in morris.js

> Attackers can inject malicious scripts into Morris.js graph labels, leading to client-side code execution when the graph is viewed.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fwx5-5fqj-jv98

## What is CVE-2017-16022?

CVE-2017-16022 is a medium-severity cross-site scripting vulnerability in HackerOne Morris.js node module, published on 4 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Morris.js creates an svg graph, with labels that appear when hovering over a point. The hovering label names are not escaped in versions 0.5.0 and earlier. If control over the labels is obtained, script can be injected. The script will run on the client side whenever that specific graph is loaded.

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

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

2 open source packages ship an affected version, including morris.js. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `morris.js` | npm | All versions | None |
| `morris.js` | npm | All versions | None |

Products: Morris.js Project Morris.js.

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

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

## Is CVE-2017-16022 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16022 is a medium-severity cross-site scripting vulnerability in HackerOne Morris.js node module, published on 4 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-16022 in the wild and no public exploit code.

Affected packages and fixed versions:
- morris.js (npm): affected all versions; no fix listed
- morris.js (npm): affected all versions; no fix listed

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

## Sources

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

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