ws モジュールにおけるバッファエラーの脆弱性
| Title |
ws モジュールにおけるバッファエラーの脆弱性
|
| Summary |
ws モジュールには、バッファエラーの脆弱性が存在します。
|
| Possible impacts |
情報を取得される可能性があります。 |
| Solution |
ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date |
Jan. 4, 2016, midnight |
| Registration Date |
Aug. 16, 2018, 3:10 p.m. |
| Last Update |
Aug. 16, 2018, 3:10 p.m. |
|
CVSS3.0 : 重要
|
| Score |
7.5
|
| Vector |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
|
CVSS2.0 : 警告
|
| Score |
5
|
| Vector |
AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected System
CVE (情報セキュリティ 共通脆弱性識別子)
CWE (共通脆弱性タイプ一覧)
ベンダー情報
Change Log
| No |
Changed Details |
Date of change |
| 1 |
[2018年08月16日] 掲載 |
Aug. 16, 2018, 3:10 p.m. |
NVD Vulnerability Information
CVE-2016-10518
| Summary |
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.
|
| Publication Date |
June 1, 2018, 5:29 a.m. |
| Registration Date |
Jan. 26, 2021, 2:05 p.m. |
| Last Update |
Nov. 21, 2024, 11:44 a.m. |
Affected software configurations
| Configuration1 |
or higher |
or less |
more than |
less than |
| cpe:2.3:a:ws_project:ws:*:*:*:*:*:node.js:*:* |
|
|
|
1.0.1 |
Related information, measures and tools
Common Vulnerabilities List