Quick answers
- Is CVE-2020-24807 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-24807 being exploited in the wild.
- How severe is CVE-2020-24807?
- Low severity, with a CVSS score of 3.1, published 2 October 2020.
- Which products and versions are affected?
- socket.io-file (npm) SEMVER:introduced=0,last_affected=2.0.31.
- Is there a fix for CVE-2020-24807?
- 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 CVE-2020-24807 attacked?
- It is attacked with local access.
- Am I affected by CVE-2020-24807?
- 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
The vulnerability is a client-side validation bypass (CWE-20: Improper Input Validation). File type restrictions are enforced only in the browser client, not on the server side. An attacker can intercept WebSocket traffic after client-side validation passes and modify the filename parameter to upload files of forbidden types. This requires network access to the WebSocket connection and user interaction to initiate an upload, but the attacker can then alter the request to upload malicious files. No patch has been released as of the advisory publication date.
Affected products
- Rico socket.io-file 0–2.0.31
Identifiers
- CVE-2020-24807
- GHSA-6495-8jvh-f28x
Timeline
- 2020-10-02: disclosed
- 2020-10-02: advisory