PT-2025-38575 · Unknown · Aliasvault Api

Filippo Decortes · Published 2025-09-19 · Updated 2025-09-19 · CVE-2025-59344

Positive Technologies (AI Summary)

CVSS v3.1

7.7

High

Base vector

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Name of the Vulnerable Software and Affected Versions AliasVault API versions 0.23.0 and lower

Description A server-side request forgery (SSRF) vulnerability exists in the favicon extraction feature. The extractor fetches a user-supplied URL, parses the returned HTML, and follows <link rel="icon" href="…". While the initial URL is validated to allow only HTTP/HTTPS with default ports, the extractor automatically follows redirects and does not block requests to loopback or internal IP ranges. An authenticated, low-privileged user can exploit this behavior to coerce the backend into making HTTP(S) requests to arbitrary internal hosts and non-default ports. If the target host serves a favicon or any other valid image, the response is returned to the attacker in Base64 form. Timing and error behavior can be abused to map internal services. This vulnerability only affects self-hosted AliasVault instances reachable from the public internet with public user registration enabled.

Recommendations Upgrade to AliasVault version 0.23.1 or later.

Exploit

Fix

SSRF

Weakness Enumeration

CWE-918

Related Identifiers

CVE-2025-59344

GHSA-F253-F7XC-W7PJ

Affected Products

Aliasvault Api

References · 10

• 🔥 https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/59xxx/CVE-2025-59344.json · Exploit
• https://osv.dev/vulnerability/CVE-2025-59344 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2025-59344 · Security Note
• https://github.com/aliasvault/aliasvault/pull/1226 · Note
• https://github.com/aliasvault/aliasvault/security/advisories/GHSA-f253-f7xc-w7pj · Note
• https://github.com/aliasvault/aliasvault/releases/tag/0.23.1 · Note
• https://github.com/aliasvault/aliasvault/commit/58c39815e4c8bb27a311c3b592d54e157b4e6968 · Note
• https://twitter.com/VulmonFeeds/status/1969084481408524759 · Twitter Post
• https://twitter.com/CVEnew/status/1969110887048102348 · Twitter Post
• https://t.me/CVEtracker/32958 · Telegram Post