CVE-2017-16031
unknown
CVSS v3
—
CVSS v4 NEW
—
VIR risk
—
Description
Insecure randomness in socket.io
Predictions
Exploit likelihood
30%
Patch ETA
—
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| npm | socket.io | <0.9.7 | 0.9.7 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2017-16031
- https://github.com/socketio/socket.io/issues/856
- https://github.com/socketio/socket.io/pull/857
- https://github.com/socketio/socket.io/commit/67b4eb9abdf111dfa9be4176d1709374a2b4ded8
- https://github.com/advisories/GHSA-qv2v-m59f-v5fw
- https://github.com/socketio/socket.io
- https://www.npmjs.com/advisories/321
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.