# CVE-2020-7764: Web Cache Poisoning

> Attackers can cause denial of service via web cache poisoning using the Accept-Version header in the find-my-way routing library.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jgrh-5m3h-9c5f, SNYK-JS-FINDMYWAY-1038269

## What is CVE-2020-7764?

CVE-2020-7764 is a medium-severity vulnerability in find-my-way, published on 8 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects the package find-my-way before 2.2.5, from 3.0.0 and before 3.0.5. It accepts the Accept-Version' header by default, and if versioned routes are not being used, this could lead to a denial of service. Accept-Version can be used as an unkeyed header in a cache poisoning attack.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2020-7764?

4 open source packages ship an affected version, including find-my-way. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `find-my-way` | npm | All versions | 2.2.5 |
| `find-my-way` | npm | All versions | 2.2.5 |
| `find-my-way` | npm | From 3.0.0 | 3.0.5 |
| `find-my-way` | npm | From 3.0.0 | 3.0.5 |

Products: Find-My-Way Project Find-My-Way.

## How do I fix CVE-2020-7764?

Upgrade find-my-way to a fixed version for your release line: 2.2.5 or 3.0.5.

## Is CVE-2020-7764 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7764 and fix it if it is affected.

What it is: CVE-2020-7764 is a medium-severity vulnerability in find-my-way, published on 8 Nov 2020. 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-2020-7764 in the wild and no public exploit code.

Affected packages and fixed versions:
- find-my-way (npm): affected all versions; fixed in 2.2.5
- find-my-way (npm): affected all versions; fixed in 2.2.5
- find-my-way (npm): affected from 3.0.0; fixed in 3.0.5
- find-my-way (npm): affected from 3.0.0; fixed in 3.0.5

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

## Sources

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

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