CVE-2017-16031

Name: CVE-2017-16031
Creator: NVD / NIST
Published: 2018-06-04T19:29:01.727+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 2.00%

Last modified Jun 17, 2026

CVE-2017-16031 is a vulnerability of currently unknown severity. Socket.io is a realtime application framework that provides communication via websockets. Because socket.io 0.9.6 and earlier depends on `Math.random()` to create socket IDs, the IDs are predictable. EPSS estimates a 2.00% chance of exploitation in the next 30 days.

Description

Socket.io is a realtime application framework that provides communication via websockets. Because socket.io 0.9.6 and earlier depends on `Math.random()` to create socket IDs, the IDs are predictable. An attacker is able to guess the socket ID and gain access to socket.io servers, potentially obtaining sensitive information.

Metrics

EPSS Probability

2.00%

78.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-330

Affected Software

Vendor	Product	Versions
Socket	Socket.Io	<= 0.9.6

References

https://github.com/socketio/socket.io/commit/67b4eb9abdf111dfa9be4176d1709374a2b4ded8Issue Tracking, Patch, Third Party Advisory
https://github.com/socketio/socket.io/issues/856Issue Tracking, Third Party Advisory
https://github.com/socketio/socket.io/pull/857Issue Tracking, Third Party Advisory
https://nodesecurity.io/advisories/321Third Party Advisory
https://github.com/socketio/socket.io/commit/67b4eb9abdf111dfa9be4176d1709374a2b4ded8Issue Tracking, Patch, Third Party Advisory
https://github.com/socketio/socket.io/issues/856Issue Tracking, Third Party Advisory
https://github.com/socketio/socket.io/pull/857Issue Tracking, Third Party Advisory
https://nodesecurity.io/advisories/321Third Party Advisory

Timeline

Published: Jun 4, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-16031?

How severe is CVE-2017-16031?

Severity scoring for CVE-2017-16031 is pending analysis. The EPSS model estimates a 2.00% probability of exploitation in the next 30 days.

How do I fix CVE-2017-16031?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-16031?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST