GHSA-c96f-x56v-gq3hHighCVSS 7.5
find-my-way: DDoS with HTTP2
🔗 CVE IDs covered (1)
📋 Description
Impact
Remotely triggerable DoS in find-my-way when it is used with Node's HTTP/2 server.
The short version is that lookup() passes req.method into find(), and find() indexes this.trees[method]. Since this.trees is a normal object, HTTP/2 method values like constructor, toString, or __proto__ can resolve inherited object properties instead of returning undefined. The code then treats that value like a router node and crashes when it reaches currentNode.prefix.length.
Patches
Upgrade to v9.7.0.
Workarounds
Do not use find-my-way with HTTP/2 servers, or validate that the http method is valid beforehand.
🎯 Affected products1
- npm/find-my-way:<= 9.6.0
🔗 References (5)
- https://github.com/delvedor/find-my-way/security/advisories/GHSA-c96f-x56v-gq3h
- https://github.com/delvedor/find-my-way/pull/434
- https://github.com/delvedor/find-my-way/commit/cfe3fd6168b5ac1594c0820fb83fce251a533fc1
- https://github.com/delvedor/find-my-way/releases/tag/v9.7.0
- https://github.com/advisories/GHSA-c96f-x56v-gq3h