Vulnerability-Lookup

CNVD-2018-19056

Vulnerability from cnvd - Published: 2018-09-17

Title

ws模块远程内存泄露漏洞

Description

ws module是一款Node.js WebSocket服务器的实现。 ws模块1.0.0之前版本中的ping功能存在安全漏洞。攻击者可利用该漏洞使ws向服务器发送已被分配使用的缓冲区中的内容，泄露敏感信息。

Severity

中

Patch Name

ws模块远程内存泄露漏洞的补丁

Patch Description

ws module是一款Node.js WebSocket服务器的实现。 ws模块1.0.0之前版本中的ping功能存在安全漏洞。攻击者可利用该漏洞使ws向服务器发送已被分配使用的缓冲区中的内容，泄露敏感信息。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description

目前厂商已发布升级补丁以修复漏洞，补丁获取链接： https://github.com/websockets/ws/releases/tag/1.0.1

Reference

https://gist.github.com/c0nrad/e92005446c480707a74a

Impacted products

Name
ws module ws module <1.0.0

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-10518",
      "cveUrl": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10518"
    }
  },
  "description": "ws module\u662f\u4e00\u6b3eNode.js WebSocket\u670d\u52a1\u5668\u7684\u5b9e\u73b0\u3002\r\n\r\nws\u6a21\u57571.0.0\u4e4b\u524d\u7248\u672c\u4e2d\u7684ping\u529f\u80fd\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u4f7fws\u5411\u670d\u52a1\u5668\u53d1\u9001\u5df2\u88ab\u5206\u914d\u4f7f\u7528\u7684\u7f13\u51b2\u533a\u4e2d\u7684\u5185\u5bb9\uff0c\u6cc4\u9732\u654f\u611f\u4fe1\u606f\u3002",
  "discovererName": "unknwon",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://github.com/websockets/ws/releases/tag/1.0.1",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-19056",
  "openTime": "2018-09-17",
  "patchDescription": "ws module\u662f\u4e00\u6b3eNode.js WebSocket\u670d\u52a1\u5668\u7684\u5b9e\u73b0\u3002\r\n\r\nws\u6a21\u57571.0.0\u4e4b\u524d\u7248\u672c\u4e2d\u7684ping\u529f\u80fd\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u4f7fws\u5411\u670d\u52a1\u5668\u53d1\u9001\u5df2\u88ab\u5206\u914d\u4f7f\u7528\u7684\u7f13\u51b2\u533a\u4e2d\u7684\u5185\u5bb9\uff0c\u6cc4\u9732\u654f\u611f\u4fe1\u606f\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "ws\u6a21\u5757\u8fdc\u7a0b\u5185\u5b58\u6cc4\u9732\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "ws module ws module \u003c1.0.0"
  },
  "referenceLink": "https://gist.github.com/c0nrad/e92005446c480707a74a",
  "serverity": "\u4e2d",
  "submitTime": "2018-06-07",
  "title": "ws\u6a21\u5757\u8fdc\u7a0b\u5185\u5b58\u6cc4\u9732\u6f0f\u6d1e"
}

CVE-2016-10518 (GCVE-0-2016-10518)

Vulnerability from cvelistv5 – Published: 2018-05-31 20:00 – Updated: 2024-09-17 02:57

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.

Severity

No CVSS data available.

CWE

CWE-201 - Information Exposure Through Sent Data (CWE-201)

Assigner

hackerone mitre root

References

3 references

URL	Tags
https://github.com/websockets/ws/releases/tag/1.0.1	x_refsource_MISC
https://nodesecurity.io/advisories/67	x_refsource_MISC
https://gist.github.com/c0nrad/e92005446c480707a74a	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version
HackerOne	ws node module	Affected: <= 1.0.0

Date Public

2018-04-26 00:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-06T03:21:52.139Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/websockets/ws/releases/tag/1.0.1"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://nodesecurity.io/advisories/67"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://gist.github.com/c0nrad/e92005446c480707a74a"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "ws node module",
          "vendor": "HackerOne",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c= 1.0.0"
            }
          ]
        }
      ],
      "datePublic": "2018-04-26T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027t 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."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-201",
              "description": "Information Exposure Through Sent Data (CWE-201)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2018-05-31T19:57:01.000Z",
        "orgId": "36234546-b8fa-4601-9d6f-f4e334aa8ea1",
        "shortName": "hackerone"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/websockets/ws/releases/tag/1.0.1"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://nodesecurity.io/advisories/67"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://gist.github.com/c0nrad/e92005446c480707a74a"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "support@hackerone.com",
          "DATE_PUBLIC": "2018-04-26T00:00:00",
          "ID": "CVE-2016-10518",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "ws node module",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "\u003c= 1.0.0"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "HackerOne"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "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\u0027t 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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "Information Exposure Through Sent Data (CWE-201)"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/websockets/ws/releases/tag/1.0.1",
              "refsource": "MISC",
              "url": "https://github.com/websockets/ws/releases/tag/1.0.1"
            },
            {
              "name": "https://nodesecurity.io/advisories/67",
              "refsource": "MISC",
              "url": "https://nodesecurity.io/advisories/67"
            },
            {
              "name": "https://gist.github.com/c0nrad/e92005446c480707a74a",
              "refsource": "MISC",
              "url": "https://gist.github.com/c0nrad/e92005446c480707a74a"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "36234546-b8fa-4601-9d6f-f4e334aa8ea1",
    "assignerShortName": "hackerone",
    "cveId": "CVE-2016-10518",
    "datePublished": "2018-05-31T20:00:00.000Z",
    "dateReserved": "2017-10-29T00:00:00.000Z",
    "dateUpdated": "2024-09-17T02:57:19.095Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

CNVD-2018-19056

CVE-2016-10518 (GCVE-0-2016-10518)

Tags

Sightings

Nomenclature

Related by attack behaviour