# CVE-2020-24807: File restriction bypass in socket.io-file

> Remote attackers can execute arbitrary code by uploading executable files due to client-side validation bypass in the socket.io-file package.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6495-8jvh-f28x

## What is CVE-2020-24807?

CVE-2020-24807 is a high-severity vulnerability in n/a, published on 6 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The socket.io-file package through 2.0.31 for Node.js relies on client-side validation of file types, which allows remote attackers to execute arbitrary code by uploading an executable file via a modified JSON name field. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2020-24807?

2 open source packages ship an affected version, including socket.io-file. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `socket.io-file` | npm | All versions to 2.0.31 | None |
| `socket.io-file` | npm | All versions to 2.0.31 | None |

Products: Socket.io-File Project Socket.io-File.

## How do I fix CVE-2020-24807?

No fix has been published for CVE-2020-24807 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-24807 being exploited?

There is no known exploitation of CVE-2020-24807 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-15779](https://insights.sbomify.com/CVE-2020-15779/): Path Traversal in socket.io-file (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24807 and fix it if it is affected.

What it is: CVE-2020-24807 is a high-severity vulnerability in n/a, published on 6 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-24807 in the wild and no public exploit code.

Affected packages and fixed versions:
- socket.io-file (npm): affected all versions up to 2.0.31; no fix listed
- socket.io-file (npm): affected all versions up to 2.0.31; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-24807/ (Markdown: https://insights.sbomify.com/CVE-2020-24807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-24807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-24807
- OSV: https://osv.dev/vulnerability/CVE-2020-24807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-24807/
Summaries are generated and may contain mistakes; the official description above is the record.