rustfs
Affected
- introduced
1.0.0-alpha.1, fixed1.0.0-alpha.80(semver)
Fixed versions
1.0.0-alpha.80
Fix
- Fixed version
1.0.0-alpha.80cargo update -p rustfs --precise 1.0.0-alpha.80
Advisory
Also known as: CVE-2026-22782
RustFS's RPC signature verification logs shared secret
Summary
Invalid RPC signatures cause the server to log the shared HMAC secret (and expected signature), which exposes the secret to log readers and enables forged RPC calls.
Details
In `crates/ecstore/src/rpc/http_auth.rs:115-122` , the invalid signature branch logs sensitive data:
if signature != expected_signature {
error!(
"verify_rpc_signature: Invalid signature: secret {}, url {}, method {}, timestamp {}, signature {}, expected_signature {}",
secret, url, method, timestamp, signature, expected_signature
);
return Err(std::io::Error::other("Invalid signature"));
}
This log line includes secret and expected_signature, both derived from the shared HMAC key. Any invalidly signed request triggers this path. The function is reachable from RPC and admin request handlers.
PoC
ts=$(date +%s) curl -v \ -H "x-rustfs-timestamp: $ts" \ -H "x-rustfs-signature: invalid-signature" \ "http://localhost:9000/rustfs/rpc/read_file_stream?disk=foo&volume=bar&path=baz&offset=0&length=1"HTTP 403 AccessDenied: Invalid signature verify_rpc_signature: Invalid signature: secret rustfsadmin, url /rustfs/rpc/read_file_stream?disk=foo&volume=bar&path=baz&offset=0&length=1, method GET, timestamp 1767852115, signature invalid-signature, expected_signature oisNxNRTb80GXf97s/PGdScJzu8QB9Oxs+uOwf8RiK8=Impact
Low Basis: The source's own band: LOW
1.0.0-alpha.1, fixed 1.0.0-alpha.80 (semver)1.0.0-alpha.80
1.0.0-alpha.80cargo update -p rustfs --precise 1.0.0-alpha.80Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0