CVE-2016-10536

Published May 31, 2018 CVSS 3.0 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
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. This is problematic as engine.io-client 1.6.8 and earlier 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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2019-0221 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. This is problematic as engine.io-client 1.6.8 and earlier 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.
Github GHSA Github GHSA GHSA-4r4m-hjwj-43p8 Insecure Defaults Allow MITM Over TLS in engine.io-client
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
hackerone
Published
Updated
Sep 17, 2024, 1:46 AM
Reserved
Oct 29, 2017, 12:00 AM
Status
Modified
Published
May 31, 2018, 8:29 PM
Modified
Jun 17, 2026, 12:39 AM