Do Son 
TL;DR
Security researchers have uncovered two critical vulnerabilities leading to a complete Rclone auth proxy bypass. These flaws enable remote attackers to circumvent authentication mechanisms entirely. Consequently, administrators must apply the latest patches immediately to secure their cloud storage environments.
Why It Matters
Rclone serves as a popular command-line utility for managing and syncing files across various cloud storage providers. A successful Rclone auth proxy bypass grants unauthorized users complete access to sensitive data stored in these environments. The details of the vulnerability and the proof-of-concept exploit code have been publicly disclosed. This public availability significantly increases the risk of active exploitation. Unauthenticated attackers can read, modify, or delete critical files across connected backend systems. Furthermore, organizations exposing these specific configurations to the public internet face immediate danger. The first flaw carries a critical severity score of 9.8, highlighting the extreme risk to unpatched deployments. Because the attack requires no user interaction, automated exploitation is highly likely.
How The Attack Works
The first vulnerability centers on a severe signature verification flaw. When administrators configure the –auth-proxy flag without the –auth-key option, the server fails to validate incoming requests correctly. The middleware extracts the access key ID directly from the client’s authorization header and registers it with an empty secret. As noted in the security advisory, “an empty string is a valid HMAC key, so a caller can trivially compute a correct SigV4 signature for ANY access key ID of their choosing using an empty secret.” The proxy script never receives a real secret to verify against. This allows the attacker to forge a fully authenticated bucket listing without any prior credential knowledge.
The second vulnerability involves an option parsing mismatch during remote control server startup. The server constructors check a global proxy setting instead of the specific per-server configuration. The advisory explains that “when the process-global option is empty… the supplied authentication proxy is silently ignored.” As a result, the system falls back to a default state. For FTP servers, this fallback allows anonymous logins with full read and write permissions. For S3 servers, it allows authorized users to reach a fixed filesystem rather than their restricted backend.
Affected Versions
These security flaws impact multiple versions of the Rclone utility across different deployment modes. The severe SigV4 signature bypass affects all Rclone versions up to and including version 1.68.0. The RC per-server auth proxy bypass affects versions 1.70.0 through 1.75.0. It also impacts the development commit 5629f2668c69149bf3d9d8e2a25bb32a2648606e. Dedicated command-line interface commands utilizing process-global options are not affected by the parsing mismatch.
Patch Or Mitigation Steps
Developers have released an official fix to address both vulnerabilities. Users must upgrade to Rclone version 1.75.1 immediately. The patched version refuses to start the S3 server when the auth proxy is set without the required authentication key. Additionally, the update corrects the option checking logic to use the proper per-server configuration rather than global settings. If you cannot update right away, you should ensure that the –auth-key parameter is always explicitly defined in your setup. You must also avoid exposing remotely controlled FTP or S3 servers to untrusted networks. Finally, review your access logs for suspicious administrative activity or unexpected bucket listings.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!
Buy Me a Coffee
