CVE-2016-10518
Remote Memory Disclosure in ws
Reported by hackerone · Published May 31, 2018
A vulnerability was found in the ping functionality of the ws module before 1.0.0 which allowed clients to allocate memory by sending a ping frame. The ping functionality by default responds with a pong frame and the previously given payload of the ping frame. This is exactly what you expect, but internally ws always transforms all data that we need to send to a Buffer instance and that is where the vulnerability existed. ws didn't do any checks for the type of data it was sending. With buffers in node when you allocate it when a number instead of a string it will allocate the amount of bytes.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| HackerOne | ws node module | <= 1.0.0 |
| npm | ws | 0 |
| HackerOne | ws node module | 0 |
| ws_project | ws |
Timeline
- May 31, 2018 CVE Published
- Feb 4, 2022 EPSS Score (30 in total, the first dated here)
- Sep 17, 2024 CVE Updated
- Mar 10, 2026 Security Advisory
- Oct 10, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2016-10518
vulnetix vdb fixes CVE-2016-10518
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2016-10518/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- x_refsource_MISC
- x_refsource_MISC
- x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2016-10518 advisory
- https://github.com/advisories/GHSA-2mhh-w6q8-5hxw advisory
- https://www.npmjs.com/advisories/67 url