# CVE-2024-52793: XSS vulnerability in serveDir API of @std/http/file-server on POSIX systems

> An attacker controlling file names can execute arbitrary scripts in browsers viewing directory listings via the Deno std http file-server.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Nov 2024
- **Updated:** 26 Nov 2024

## What is CVE-2024-52793?

CVE-2024-52793 is a medium-severity cross-site scripting vulnerability in denoland std, published on 22 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Deno Standard Library provides APIs for Deno and the Web. Prior to version 1.0.11, `http/file-server`'s `serveDir` with `showDirListing: true` option is vulnerable to cross-site scripting when the attacker is a user who can control file names in the source directory on systems with POSIX file names. Exploitation might also be possible on other systems but less trivial due to e.g. lack of file name support for `<>` in Windows. Version 1.0.11 fixes the issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-52793?


## How do I fix CVE-2024-52793?

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

## Is CVE-2024-52793 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52793 and fix it if it is affected.

What it is: CVE-2024-52793 is a medium-severity cross-site scripting vulnerability in denoland std, published on 22 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-52793 in the wild and no public exploit code.

Affected product: denoland std. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-52793/ (Markdown: https://insights.sbomify.com/CVE-2024-52793/index.md)
```

## Sources

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

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