Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2016-10536

5.9 · MEDIUM
Published May 31, 2018 socket CWE-300 EPSS 1.01% (61th pctl)

Overview

CVE-2016-10536 is a medium-severity vulnerability affecting socket engine.io-client. It was published on May 31, 2018 and has a CVSS 3.0 base score of 5.9 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 5.9, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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

Check the references section for vendor advisories and patches from socket. Update engine.io-client to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
socket engine.io-client 0 Affected

Frequently Asked Questions

What is CVE-2016-10536?

CVE-2016-10536 is a medium-severity vulnerability affecting socket engine.io-client. It was published on May 31, 2018 and has a CVSS 3.0 base score of 5.9 (MEDIUM).

How severe is CVE-2016-10536?

This vulnerability has a CVSS 3.0 base score of 5.9, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-10536?

Check the references section for vendor advisories and patches from socket. Update engine.io-client to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-10536?

CyberStrike's AI-powered security agents can automatically detect CVE-2016-10536 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.