PT-2026-6478 · Crates.Io · Salvo
Publicado
2026-01-08
·
Atualizado
2026-01-08
CVSS v3.1
8.8
Alta
| Vetor | AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L |
Summary
The function
list html generates an file view of a folder which includes a render of the current path, in which its inserted in the HTML without proper sanitation, leading to reflected XSS. The request path is decoded and normalized in the matching stage but is not inserted raw in the HTML view (current.path). The only constraint here is for the root path (e.g., /files in the PoC example) to have a subdirectory (e. g., common ones like styles/scripts/etc.) so that the matching returns the list HTML page instead of the Not Found page.Details
The vulnerable snippet of code is the following:
dir.rs
rust
// ... fn list html(...
let mut ftxt = format!(
r#"<!DOCTYPE html><html><head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>{}</title>
<style>{}</style></head><body><header><h3>Index of: {}</h3></header><hr/>"#,
current.path,
HTML STYLE,
header links(¤t.path)
);
// ...As seen here
<title>{}</title> it is inserted unsafely.PoC
Here is the example app, note this doesn’t need an upload feature (e.g to the other reported vulnerability), only the sub-folder is required.
main.rsrust
use salvo::prelude::*;
use salvo::serve static::StaticDir;
use tokio::fs;
#[tokio::main]
async fn main() {
tracing subscriber::fmt().init();
fs::create dir all("uploads").await.expect("create uploads dir");
let router = Router::new()
.push(
Router::with path("files/{**rest path}")
.get(StaticDir::new("uploads").auto list(true)),
);
let acceptor = TcpListener::new("127.0.0.1:5800").bind().await;
Server::new(acceptor).serve(router).await;
}Cargo.tomlrust
[package]
name = "salvo-staticdir-xss-poc"
version = "0.1.0"
edition = "2024"
[dependencies]
salvo = { version = "0.85.0", features = ["serve-static"] }
tokio = { version = "1", features = ["macros", "rt-multi-thread", "fs"] }
tracing-subscriber = "0.3"Setup commands:
bash
mkdir uploads
mkdir uploads/blaImpact
JavaScript execution, most likely leading to an account takeover, depending on the site's constraint (CSP, etc…).
Correção
XSS
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾
Enumeração de Fraquezas
Identificadores relacionados
Produtos afetados
Salvo