CVE-2016-10518
WebSockets Buffer Overwrite Vulnerability in ws Ping Functionality
Description
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.
INFO
Published Date :
May 31, 2018, 8:29 p.m.
Last Modified :
Nov. 21, 2024, 2:44 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
3.9
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2016-10518.
| URL | Resource |
|---|---|
| https://gist.github.com/c0nrad/e92005446c480707a74a | Patch Third Party Advisory |
| https://github.com/websockets/ws/releases/tag/1.0.1 | Release Notes Third Party Advisory |
| https://nodesecurity.io/advisories/67 | Third Party Advisory |
| https://gist.github.com/c0nrad/e92005446c480707a74a | Patch Third Party Advisory |
| https://github.com/websockets/ws/releases/tag/1.0.1 | Release Notes Third Party Advisory |
| https://nodesecurity.io/advisories/67 | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2016-10518 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2016-10518 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Oct. 09, 2019
Action Type Old Value New Value Added CWE HackerOne CWE-201 -
Initial Analysis by [email protected]
Aug. 01, 2018
Action Type Old Value New Value Added CVSS V2 (AV:N/AC:L/Au:N/C:P/I:N/A:N) Added CVSS V3 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Changed Reference Type https://gist.github.com/c0nrad/e92005446c480707a74a No Types Assigned https://gist.github.com/c0nrad/e92005446c480707a74a Patch, Third Party Advisory Changed Reference Type https://github.com/websockets/ws/releases/tag/1.0.1 No Types Assigned https://github.com/websockets/ws/releases/tag/1.0.1 Release Notes, Third Party Advisory Changed Reference Type https://nodesecurity.io/advisories/67 No Types Assigned https://nodesecurity.io/advisories/67 Third Party Advisory Added CWE CWE-119 Added CPE Configuration OR *cpe:2.3:a:ws_project:ws:*:*:*:*:*:node.js:*:* versions up to (excluding) 1.0.1
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2016-10518 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2016-10518
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.15 }} 0.00%
score
0.51506
percentile