# CVE-2017-16202: cofeescript is malware

> The CoffeeScript npm module exfiltrates sensitive user data like SSH keys and bash history to a third-party server during installation.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-m6wh-m8m8-6xx5

## What is CVE-2017-16202?

CVE-2017-16202 is a high-severity vulnerability in HackerOne coffeescript node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The cofeescript module exfiltrates sensitive data such as a user's private SSH key and bash history to a third party server during installation.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-506 (Embedded Malicious Code)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cofeescript` | npm | All versions | None |
| `cofeescript` | npm | All versions | None |

Products: Cofeescript Project Cofeescript.

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

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

## Is CVE-2017-16202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16202 is a high-severity vulnerability in HackerOne coffeescript node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16202 in the wild and no public exploit code.

Affected packages and fixed versions:
- cofeescript (npm): affected all versions; no fix listed
- cofeescript (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-16202/ (Markdown: https://insights.sbomify.com/CVE-2017-16202/index.md)
```

## Sources

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

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