gsd-2016-10518
Vulnerability from gsd
Modified
2023-12-13 01:21
Details
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.
Aliases
Aliases
CVE-2016-10518


To clipboard 

{
   GSD: {
      alias: "CVE-2016-10518",
      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.",
      id: "GSD-2016-10518",
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2016-10518",
         ],
         details: "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.",
         id: "GSD-2016-10518",
         modified: "2023-12-13T01:21:27.080616Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         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: "<= 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'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.",
               },
            ],
         },
         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",
               },
            ],
         },
      },
      "gitlab.com": {
         advisories: [
            {
               affected_range: "<1.0.1",
               affected_versions: "All versions before 1.0.1",
               cvss_v2: "AV:N/AC:L/Au:N/C:P/I:N/A:N",
               cvss_v3: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
               cwe_ids: [
                  "CWE-1035",
                  "CWE-119",
                  "CWE-937",
               ],
               date: "2021-01-08",
               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.",
               fixed_versions: [
                  "1.0.1",
               ],
               identifier: "CVE-2016-10518",
               identifiers: [
                  "GHSA-2mhh-w6q8-5hxw",
                  "CVE-2016-10518",
               ],
               not_impacted: "All versions starting from 1.0.1",
               package_slug: "npm/ws",
               pubdate: "2019-02-18",
               solution: "Upgrade to version 1.0.1 or above.",
               title: "Improper Restriction of Operations within the Bounds of a Memory Buffer",
               urls: [
                  "https://nvd.nist.gov/vuln/detail/CVE-2016-10518",
                  "https://gist.github.com/c0nrad/e92005446c480707a74a",
                  "https://github.com/advisories/GHSA-2mhh-w6q8-5hxw",
                  "https://github.com/websockets/ws/releases/tag/1.0.1",
                  "https://www.npmjs.com/advisories/67",
                  "https://nodesecurity.io/advisories/67",
               ],
               uuid: "f041dd9f-3230-4123-9e8f-39180b1f3249",
            },
         ],
      },
      "nvd.nist.gov": {
         configurations: {
            CVE_data_version: "4.0",
            nodes: [
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:a:ws_project:ws:*:*:*:*:*:node.js:*:*",
                        cpe_name: [],
                        versionEndExcluding: "1.0.1",
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
            ],
         },
         cve: {
            CVE_data_meta: {
               ASSIGNER: "cve-assignments@hackerone.com",
               ID: "CVE-2016-10518",
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     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'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.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "en",
                           value: "CWE-119",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://nodesecurity.io/advisories/67",
                     refsource: "MISC",
                     tags: [
                        "Third Party Advisory",
                     ],
                     url: "https://nodesecurity.io/advisories/67",
                  },
                  {
                     name: "https://github.com/websockets/ws/releases/tag/1.0.1",
                     refsource: "MISC",
                     tags: [
                        "Release Notes",
                        "Third Party Advisory",
                     ],
                     url: "https://github.com/websockets/ws/releases/tag/1.0.1",
                  },
                  {
                     name: "https://gist.github.com/c0nrad/e92005446c480707a74a",
                     refsource: "MISC",
                     tags: [
                        "Patch",
                        "Third Party Advisory",
                     ],
                     url: "https://gist.github.com/c0nrad/e92005446c480707a74a",
                  },
               ],
            },
         },
         impact: {
            baseMetricV2: {
               acInsufInfo: true,
               cvssV2: {
                  accessComplexity: "LOW",
                  accessVector: "NETWORK",
                  authentication: "NONE",
                  availabilityImpact: "NONE",
                  baseScore: 5,
                  confidentialityImpact: "PARTIAL",
                  integrityImpact: "NONE",
                  vectorString: "AV:N/AC:L/Au:N/C:P/I:N/A:N",
                  version: "2.0",
               },
               exploitabilityScore: 10,
               impactScore: 2.9,
               obtainAllPrivilege: false,
               obtainOtherPrivilege: false,
               obtainUserPrivilege: false,
               severity: "MEDIUM",
               userInteractionRequired: false,
            },
            baseMetricV3: {
               cvssV3: {
                  attackComplexity: "LOW",
                  attackVector: "NETWORK",
                  availabilityImpact: "NONE",
                  baseScore: 7.5,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "NONE",
                  privilegesRequired: "NONE",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
                  version: "3.0",
               },
               exploitabilityScore: 3.9,
               impactScore: 3.6,
            },
         },
         lastModifiedDate: "2019-10-09T23:16Z",
         publishedDate: "2018-05-31T20:29Z",
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.