AliasVault: Server-Side Request Forgery via DNS rebinding in Favicon Extraction
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
AliasVault is a privacy-first password manager with built-in email aliasing. Prior to 0.30.3, the AliasVault server API favicon extractor validates a user-supplied hostname with a first DNS lookup but allows the HTTP client to perform a second DNS lookup when connecting. An authenticated low-privileged user operating an attacker-controlled authoritative DNS server can return a public address during validation and a private address during connection, causing a publicly reachable self-hosted server to issue HTTP or HTTPS requests to internal hosts. A valid image response is returned in Base64 form, while other responses can expose limited timing and error information for internal-network reconnaissance. Exploitation requires a publicly reachable self-hosted instance with public registration enabled, an authenticated AliasVault account, an attacker-controlled authoritative DNS server, and a resolver that permits rebinding; default checks limit requests to ports 80 and 443. The browser extensions, web application, and mobile applications are not affected. This issue is fixed in version 0.30.3.
Text from CVE List
Affected versions 4
- aliasvaultaffected: < 0.30.3CVE List
- ghcr.io/aliasvault/aliasvaultaffected: < 0.30.3CVE List
- ghcr.io/aliasvault/apiaffected: < 0.30.3CVE List
- ghcr.io/lanedirt/aliasvault-apiaffected: < 0.30.3CVE List
References 5
- github.com/aliasvault/aliasvault/commit/7eb4fee71f4582cfc80b8daea421b99d6aa9f814Fixvia CVE List
- github.com/aliasvault/aliasvault/commit/90ea7d6bb4c74ca169ee1dde3ca38b08bd0966edFixvia CVE List
- github.com/aliasvault/aliasvault/releases/tag/0.30.3Fixvia CVE List
- github.com/aliasvault/aliasvault/security/advisories/GHSA-7hm6-fj4m-pf6fAdvisoryvia CVE List
- github.com/aliasvault/aliasvault/pull/2311Referencevia CVE List