engine.io-client up to 1.6.8 on Node.js Certificate Verification certificate validation

Summaryinfo

A vulnerability identified as critical has been detected in engine.io-client up to 1.6.8 on Node.js. The affected element is an unknown function of the component Certificate Verification. The manipulation leads to certificate validation. This vulnerability is documented as CVE-2016-10536. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in engine.io-client up to 1.6.8 on Node.js (JavaScript Library). It has been rated as critical. This issue affects some unknown functionality of the component Certificate Verification. The manipulation with an unknown input leads to a certificate validation vulnerability. Using CWE to declare the problem leads to CWE-295. The product does not validate, or incorrectly validates, a certificate. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 04/26/2016. The weakness was released 05/31/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2016-10536 since 10/29/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1587.003 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 765 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• JavaScript Library

Name

• engine.io-client

Version

• 1.6.0
• 1.6.1
• 1.6.2
• 1.6.3
• 1.6.4
• 1.6.5
• 1.6.6
• 1.6.7
• 1.6.8

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion