CVE-2020-7764 json
Web Cache Poisoning
published 6y ago modified last mo. also GHSA-jgrh-5m3h-9c5f , EUVD-2020-1460
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm find-my-way 2.2.5, 3.0.5
- n/a find-my-way 2.2.5, 3.0.5
Is CVE-2020-7764 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.78% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 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 |
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | find-my-way | <2.2.5 >=3.0.0, <3.0.5 |
2.2.5 3.0.5 |
Affected products
- n/a find-my-way
Classification
- Weakness
-
- CWE-444 Inconsistent Interpretation of HTTP Requests
References
-
github.com
/delvedor/find-my-way/commit/ab408354690e6b9cf3c4724befb3b3fa4bb90aac
web, patch, third-party-advisory
-
snyk.io
/vuln/SNYK-JS-FINDMYWAY-1038269
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-7764
advisory
-
npmjs.com
/package/find-my-way
web
Sources
- CVE List CVE-2020-7764
- GitHub Advisory GHSA-jgrh-5m3h-9c5f
- NVD CVE-2020-7764
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.