Lookup for vulnerable packages by Package URL.
| Purl | pkg:npm/engine.io-client@0.8.1 |
| Type | npm |
| Namespace | |
| Name | engine.io-client |
| Version | 0.8.1 |
| Qualifiers |
|
| Subpath | |
| Is_vulnerable | true |
| Next_non_vulnerable_version | 1.6.9 |
| Latest_non_vulnerable_version | 1.6.9 |
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-una8-r1gw-yfgy |
| vulnerability_id |
VCID-una8-r1gw-yfgy |
| summary |
Improper Certificate Validation
`engine.io-client` is the client for `engine.io`, the implementation of a transport-based `cross-browser/cross-device` bi-directional communication layer for `Socket.IO.` The vulnerability is related to the way that Node.js handles the `rejectUnauthorized` setting. If the value is something that evaluates to false, certificate verification will be disabled. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2016-10536, GHSA-4r4m-hjwj-43p8
|
| risk_score |
3.1 |
| exploitability |
0.5 |
| weighted_severity |
6.2 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-una8-r1gw-yfgy |
|
| 1 |
| url |
VCID-yc5d-8y5k-bfg6 |
| vulnerability_id |
VCID-yc5d-8y5k-bfg6 |
| summary |
Insecure Defaults Allow MITM Over TLS
There's a flaw in the way that node.js handles the `rejectUnauthorized` setting. If the value is something that evaluates to false, certificate verification will be disabled. This is problematic as engine.io-client passes in an object for settings that includes the `rejectUnauthorized` property, whether it has been set or not. If the value has not been explicitly changed, it will be passed in as `null`, resulting in certificate verification being turned off. |
| references |
|
| fixed_packages |
|
| aliases |
GMS-2016-31
|
| risk_score |
null |
| exploitability |
0.5 |
| weighted_severity |
0.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-yc5d-8y5k-bfg6 |
|
|
| Fixing_vulnerabilities |
|
| Risk_score | 3.1 |
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:npm/engine.io-client@0.8.1 |