Lookup for vulnerable packages by Package URL.
| Purl | pkg:npm/ws@1.0.1 |
|---|
| Type | npm |
|---|
| Namespace | |
|---|
| Name | ws |
|---|
| Version | 1.0.1 |
|---|
| Qualifiers |
|
|---|
| Subpath | |
|---|
| Is_vulnerable | false |
|---|
| Next_non_vulnerable_version | 1.1.1 |
|---|
| Latest_non_vulnerable_version | 3.3.1 |
|---|
| Affected_by_vulnerabilities |
|
|---|
| Fixing_vulnerabilities |
| 0 |
| url |
VCID-1h47-fru4-1ugx |
| vulnerability_id |
VCID-1h47-fru4-1ugx |
| summary |
Improper Restriction of Operations within the Bounds of a Memory Buffer
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. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2016-10518, GHSA-2mhh-w6q8-5hxw
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-1h47-fru4-1ugx |
|
| 1 |
|
|
|---|
| Risk_score | null |
|---|
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:npm/ws@1.0.1 |
|---|