Error311 FileRise
FileRise: AUTH_BYPASS reverse-proxy header trust without source IP validation enables full authentication bypass
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.16.0, FileRise deployments with AUTH_BYPASS enabled trust the configured reverse-proxy identity header without verifying that the request originated from FR_TRUSTED_PROXIES. When the backend application port is reachable directly, an unauthenticated attacker can supply X-Remote-User and obtain a session for the asserted account, including an administrator account, without a password or MFA. The flaw is limited to deployments that enable proxy-header authentication and expose an untrusted path to the backend. This issue is fixed in version 3.16.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.16.0
Fixed in 3.16.0
Mitigation
Upgrade FileRise to 3.16.0 or later.
References
- Vendor advisory github.com/error311/FileRise/security/advisori…
- Patch github.com/error311/FileRise/commit/f7114ca2a4…
- Release notes github.com/error311/FileRise/releases/tag/v3.1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.