CVE-2024-32966 Stored Cross-site Scripting in directory listings via file names in static-web-server
Attackers can execute arbitrary JavaScript in the victim's browser via malicious file names when directory listings are enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2024-32966?
CVE-2024-32966 is a medium-severity cross-site scripting vulnerability in static-web-server, published on 1 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Static Web Server (SWS) is a tiny and fast production-ready web server suitable to serve static web files or assets. In affected versions if directory listings are enabled for a directory that an untrusted user has upload privileges for, a malicious file name like `<img src=x onerror=alert(1)>.txt` will allow JavaScript code execution in the context of the web server’s domain. SWS generally does not perform escaping of HTML entities on any values inserted in the directory listing. At the very least `file_name` and `current_path` could contain malicious data however. `file_uri` could also be malicious but the relevant scenarios seem to be all caught by hyper. For any web server that allow users to upload files or create directories under a name of their choosing this becomes a stored Cross-site Scripting vulnerability. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Which versions are affected by CVE-2024-32966?
2 open source packages ship an affected version, including static-web-server.
| Package | Affected | Fixed in |
|---|---|---|
static-web-server crates.io | All versions | 2.30.0 |
static-web-server crates.io | All versions | 2.30.0 |
How do I fix CVE-2024-32966?
Upgrade static-web-server to 2.30.0 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2024-32966 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32966 exists.
Sources
Also known as GHSA-rwfq-v4hq-h7fg.