Description
SeaweedFS before 4.30 reflects the callback query parameter verbatim into responses served with Content-Type application/javascript in the shared writeJson helper (weed/server/common.go), with no callback-name validation, no X-Content-Type-Options: nosniff header, and no CORS allow-list. Every JSON endpoint that uses writeJson - including the unauthenticated master endpoints /dir/status, /dir/lookup and /cluster/status, the volume server /status, and the filer directory listing, all reachable in the default configuration (no -whiteList, no security.toml, bound to 0.0.0.0) - can therefore be loaded cross-origin via a script tag with a chosen callback, letting a third-party web page read cluster topology, volume server URLs and gRPC ports, file identifiers, and directory listings. Because the callback string is reflected at the start of the body and no nosniff header is sent, MIME-sniffing clients may also interpret the reflected content as HTML.
Problem types
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Product status
Any version before 4.30
Credits
George Chen
References
github.com/seaweedfs/seaweedfs/releases/tag/4.30 (Release Notes)
github.com/seaweedfs/seaweedfs/pull/9686 (Fix PR)
github.com/...ommit/77dcb20a7485074d37340985d53103f94538abe6 (Patch Commit)
github.com/geo-chen/oss/blob/main/seaweedfs.md (Researcher Disclosure)
www.vulncheck.com/...ia-unvalidated-jsonp-callback-parameter