Bubka 2FAuth
2FAuth: Reverse Proxy Guard Trusts Client-Supplied Headers Without Proxy Verification
2FAuth is a web app to manage Two-Factor Authentication (2FA) accounts and generate their security codes. Prior to 8.0.0, when AUTHENTICATION_GUARD=reverse-proxy-guard is enabled, ReverseProxyGuard::user() reads the default REMOTE_USER identity header, or a custom identity header selected by the AUTH_PROXY_HEADER_FOR_USER configuration setting, without confirming that the request originated from a configured trusted proxy. A remote client that can reach the application directly can forge the selected identity header and authenticate as an existing user, including an administrator, gaining access to stored 2FA secrets and account or application management functions. This issue is fixed in version 8.0.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 8.0.0
Fixed in 8.0.0
Mitigation
Upgrade 2FAuth to 8.0.0 or later.
References
- Vendor advisory github.com/Bubka/2FAuth/security/advisories/GH…
- Patch github.com/Bubka/2FAuth/commit/43873cbfba44592…
- Release notes github.com/Bubka/2FAuth/releases/tag/v8.0.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.