Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 10 May 2021.
- Which products and versions are affected?
- socket.io-file (npm) SEMVER:introduced=0,last_affected=2.0.31.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked with local access, in a software library.
- Am I affected?
- Check whether you run socket.io-file (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
socket.io-file through version 2.0.31 performs file-type validation exclusively on the client side, a classic input validation bypass vulnerability (CWE-20). An attacker can intercept WebSocket traffic after client-side validation completes and modify the file name field in the JSON payload to upload files with arbitrary extensions and content. The attack requires local network access to the WebSocket connection and user interaction to trigger the upload, but results in arbitrary file upload capabilities. No patch has been released; the maintainer no longer supports this package.
Affected products
- Rico Gonçalves socket.io-file <= 2.0.31
Timeline
- 2020-10-06: disclosed
- 2021-05-10: advisory: GHSA-r2gr-fhmr-66c5 published as duplicate of GHSA-6495-8jvh-f28x
- 2026-01-22: other: Advisory withdrawn as duplicate