CVE-2016-10518

{"id": "CVE-2016-10518", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 5.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:P/I:N/A:N", "authentication": "NONE", "integrityImpact": "NONE", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": true, "impactScore": 2.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV30": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.0", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2018-05-31T20:29:00.503", "references": [{"url": "https://gist.github.com/c0nrad/e92005446c480707a74a", "tags": ["Patch", "Third Party Advisory"], "source": "support@hackerone.com"}, {"url": "https://github.com/websockets/ws/releases/tag/1.0.1", "tags": ["Release Notes", "Third Party Advisory"], "source": "support@hackerone.com"}, {"url": "https://nodesecurity.io/advisories/67", "tags": ["Third Party Advisory"], "source": "support@hackerone.com"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-119"}]}, {"type": "Secondary", "source": "support@hackerone.com", "description": [{"lang": "en", "value": "CWE-201"}]}], "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'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."}, {"lang": "es", "value": "Se ha encontrado una vulnerabilidad en la funcionalidad ping del m\u00f3dulo ws en versiones anteriores a la 1.0.0 que permite que los clientes asignen memoria mediante el env\u00edo de un frame ping. Por defecto, la funcionalidad ping responde con un frame pong y la carga \u00fatil dada anteriormente del frame ping. Esto es exactamente lo que se espera, pero, internamente, ws siempre transforma todos los datos que se necesitan enviar a una instancia Buffer, donde exist\u00eda la vulnerabilidad. ws no realiz\u00f3 ninguna comprobaci\u00f3n para el tipo de datos que estaba enviando. Con los b\u00fafers en node, cuando se asigna con un n\u00famero en lugar de una cadena, asignar\u00e1 la cantidad de bytes."}], "lastModified": "2019-10-09T23:16:41.807", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:ws_project:ws:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "3B43414F-DCBC-4117-AA15-C35957E8F5DD", "versionEndExcluding": "1.0.1"}], "operator": "OR"}]}], "sourceIdentifier": "support@hackerone.com"}