CVE-2016-10518: Buffer Overflow
First published: Thu May 31 2018(Updated: )
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.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| npm/ws | <1.0.1 | 1.0.1 |
| Ws Project Ws | <1.0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2016-10518
- https://gist.github.com/c0nrad/e92005446c480707a74a
- https://github.com/advisories/GHSA-2mhh-w6q8-5hxw (Advisory)
- https://github.com/websockets/ws/releases/tag/1.0.1
- https://www.npmjs.com/advisories/67
- https://github.com/websockets/ws/commit/29293ed11b679e0366fa0f6bb9310b330dafd795
- https://nodesecurity.io/advisories/67
Frequently Asked Questions
What is CVE-2016-10518?
CVE-2016-10518 is a remote memory disclosure vulnerability in the ping functionality of the ws module before version 1.0.1.
How does CVE-2016-10518 affect applications using the ws module?
Applications using the ws module versions prior to 1.0.1 are affected by CVE-2016-10518, which can result in the disclosure of memory contents.
How can users control the arguments of a client.ping() call to trigger CVE-2016-10518?
Certain rare circumstances allow users to control the arguments of a client.ping() call, triggering the vulnerability in the ws module before version 1.0.1.
What is the severity of CVE-2016-10518?
CVE-2016-10518 has a severity rating of 7.5 (high).
How can I fix CVE-2016-10518 vulnerability in the ws module?
To fix the CVE-2016-10518 vulnerability, update the ws module to version 1.0.1 or newer.
- collector/github-advisory-latest
- alias/GHSA-2mhh-w6q8-5hxw
- alias/CVE-2016-10518
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/remedy
- agent/severity
- agent/weakness
- agent/references
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/description
- agent/trending
- agent/tags
- agent/source
- package-manager/npm
- vendor/ws project
- canonical/ws project ws