{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59344 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59344 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59344 is a high-severity server-side request forgery vulnerability in aliasvault, published on 19 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59344 and fix it if it is affected.\n\nWhat it is: CVE-2025-59344 is a high-severity server-side request forgery vulnerability in aliasvault, published on 19 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59344 in the wild and no public exploit code.\n\nAffected product: aliasvault. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59344/ (Markdown: https://insights.sbomify.com/CVE-2025-59344/index.md)","id":"CVE-2025-59344","markdown":"https://insights.sbomify.com/CVE-2025-59344/index.md","name":"CVE-2025-59344","record":{"aliases":["GHSA-f253-f7xc-w7pj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"AliasVault password manager","requires_auth":"low_privilege","summary":"Authenticated users can exploit SSRF in AliasVault to access internal services and read data via favicon extraction.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"AliasVault is a privacy-first password manager with built-in email aliasing. A server-side request forgery (SSRF) vulnerability exists in the favicon extraction feature of AliasVault API versions 0.23.0 and lower. The extractor fetches a user-supplied URL, parses the returned HTML, and follows \u003clink rel=\"icon\" href=\"…\"\u003e. Although 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. Even when no data is returned, timing and error behavior can be abused to map internal services. This vulnerability only affects self-hosted AliasVault instances that are reachable from the public internet with public user registration enabled. Private/internal deployments without public sign-ups are not directly exploitable. This issue has been fixed in AliasVault release 0.23.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"AliasVault Vulnerable to Server-Side Request Forgery via Favicon Extraction","id":"CVE-2025-59344","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Dragonfly did not enable authentication for some Manager’s endpoints","id":"CVE-2025-59345"},"packages":[],"prev":{"headline":"tar-fs has a symlink validation bypass if destination directory is predictable with a specific tarball","id":"CVE-2025-59343"},"products":["aliasvault"],"published":"2025-09-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-19","vendors":["aliasvault"]},"summary":"Authenticated users can exploit SSRF in AliasVault to access internal services and read data via favicon extraction.","url":"https://insights.sbomify.com/CVE-2025-59344/"}