GHSA-xwwr-4h3p-r22c: rclone serve s3: --auth-proxy without --auth-key authenticates nobody - full SigV4 signature bypass
Source: github.com
rclone serve s3's handler chain, when --auth-proxy is configured, is (outermost first): authPairMiddleware -> proxyAuthMiddleware -> gofakes3's own SigV4-verifying handler. authPairMiddleware parses the accessKeyID straight out of the incoming request's own Authorization header (entirely client-controlled) and registers {accessKey: ws.s3Secret} into gofakes3's shared credential store via AddAuthKeys, for EVERY access key any client presents - not just ones previously known to the server. …
Signalsas the pipeline stamped them
High Critical vulnerability — CVSS 9.8
What to do
- Critical severity — schedule an urgent patch.
CVEKEV and EPSS where known
Get the next one first
Every story goes to Telegram and RSS the moment it is published, and the whole wire is a keyless JSON API.