CVE-2016-10536: Medium severity socket.io client vulnerability

Published May 31, 2018
·
Updated

Affected versions of engine.io-client do not verify certificates by default, and as such may be vulnerable to Man-in-the-Middle attacks.

The vulnerability is related to the way that node.js handles the rejectUnauthorized setting. If the value is something that evaluates to false, such as undefined or null, certificate verification will be disabled.

Recommendation

Update to version 1.6.9 or later.

If you are unable to upgrade, ensure all calls to socket.io to have a rejectedUnauthorized: true flag.

Other sources

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.

Affected Software

2 affected componentsFixes available
npm/engine.io-client<1.6.9
1.6.9
Socket Engine.io-client Node.js<=1.6.8

Event History

May 31, 2018
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
DescriptionWeakness
Feb 18, 2019
Advisory Published
11:39 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2016-10536?

CVE-2016-10536 is a vulnerability in engine.io-client that allows man-in-the-middle attacks due to the lack of certificate verification.

2

How does CVE-2016-10536 impact engine.io-client?

CVE-2016-10536 allows attackers to perform man-in-the-middle attacks by bypassing certificate verification in engine.io-client.

3

What is the severity of CVE-2016-10536?

CVE-2016-10536 has a severity value of 5.9, which is considered medium.

4

How can I fix CVE-2016-10536 in engine.io-client?

To fix CVE-2016-10536 in engine.io-client, upgrade to version 1.6.9 or later.

5

What is the Common Weakness Enumeration (CWE) for CVE-2016-10536?

The CWE for CVE-2016-10536 is CWE-300 (Channel Accessible by Non-Endpoint), and CWE-295 (Improper Certificate Validation).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203