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
Published May 31, 2018
7.5
HIGHCVSS 3.0
EPSS 2.02%
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.
Affected products
-
- Version <= 1.0.0StatusaffectedConstraints-
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| HackerOne | WS Node Module | n/a |
|
- < 1.0.1
No data.
No Red Hat product state for this CVE.
ws
npm
Introduced 0 Fixed 1.0.1
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| npm | ws | 0 | 1.0.1 |
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
AV:N/AC:L/Au:N/C:P/I:N/A:N
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (14 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 2.02% (0.02015) | 80.18th | v5 (v2026.06.15) |
| Jun 15, 2026 | 2.02% (0.02015) | 78.30th | v5 (v2026.06.15) |
| Mar 30, 2025 | 0.47% (0.00468) | 61.61th | v4 (v2025.03.14) |
| Mar 29, 2025 | 1.59% (0.01588) | 70.06th | v4 (v2025.03.14) |
| Mar 17, 2025 | 0.51% (0.00506) | 64.16th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.15% (0.00154) | 53.06th | v3 (v2023.03.01) |
| Jul 8, 2023 | 0.15% (0.00153) | 50.54th | v3 (v2023.03.01) |
| May 25, 2023 | 0.28% (0.00280) | 63.72th | v3 (v2023.03.01) |
| May 8, 2023 | 0.30% (0.00304) | 65.15th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.17% (0.00166) | 51.48th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.95% (0.00954) | 36.37th | v2 (v2022.01.01) |
| Sep 2, 2022 | 0.95% (0.00954) | 34.50th | v2 (v2022.01.01) |
| Apr 1, 2022 | 0.95% (0.00954) | 32.50th | v2 (v2022.01.01) |
| Feb 4, 2022 | 0.95% (0.00954) | 16.28th | v2 (v2022.01.01) |
References (7)
- https://gist.github.com/c0nrad/e92005446c480707a74a x_refsource_MISCPatchThird Party Advisory
- https://github.com/advisories/GHSA-2mhh-w6q8-5hxw Advisory
- https://github.com/websockets/ws/commit/29293ed11b679e0366fa0f6bb9310b330dafd795
- https://github.com/websockets/ws/releases/tag/1.0.1 x_refsource_MISCRelease NotesThird Party Advisory
- https://nodesecurity.io/advisories/67 x_refsource_MISCThird Party Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2016-10518
- https://www.npmjs.com/advisories/67
| Link | Providers | Tags |
|---|---|---|
| https://gist.github.com/c0nrad/e92005446c480707a74a | x_refsource_MISCPatchThird Party Advisory | |
| https://github.com/advisories/GHSA-2mhh-w6q8-5hxw | Advisory | |
| https://github.com/websockets/ws/commit/29293ed11b679e0366fa0f6bb9310b330dafd795 | ||
| https://github.com/websockets/ws/releases/tag/1.0.1 | x_refsource_MISCRelease NotesThird Party Advisory | |
| https://nodesecurity.io/advisories/67 | x_refsource_MISCThird Party Advisory | |
| https://nvd.nist.gov/vuln/detail/CVE-2016-10518 | ||
| https://www.npmjs.com/advisories/67 |
Change history (0)
No recorded changes yet.