{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65843 exists.","fix":"No fix has been published for CVE-2025-65843 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65843 is a high-severity path traversal vulnerability in n/a, published on 3 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65843 and fix it if it is affected.\n\nWhat it is: CVE-2025-65843 is a high-severity path traversal vulnerability in n/a, published on 3 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65843 exists.\n\nAffected product: n/a. 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-65843/ (Markdown: https://insights.sbomify.com/CVE-2025-65843/index.md)","id":"CVE-2025-65843","markdown":"https://insights.sbomify.com/CVE-2025-65843/index.md","name":"CVE-2025-65843","record":{"aliases":["GHSA-3h59-4588-8c38"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Aquarius Desktop","requires_auth":"none","summary":"Local attackers can exploit insecure symlink handling in support archive generation to read or modify arbitrary files, potentially exposing root-owned data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"aquarius","vendor":"acustica-audio"}],"cvss":{"score":7.7,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Aquarius Desktop 3.0.069 for macOS contains an insecure file handling vulnerability in its support data archive generation feature. The application follows symbolic links placed inside the ~/Library/Logs/Aquarius directory and treats them as regular files. When building the support ZIP, Aquarius recursively enumerates logs using a JUCE directory iterator configured to follow symlinks, and later writes file data without validating whether the target is a symbolic link. A local attacker can exploit this behavior by planting symlinks to arbitrary filesystem locations, resulting in unauthorized disclosure or modification of arbitrary files. When chained with the associated HelperTool privilege escalation issue, root-owned files may also be exposed.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2025-65843","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2025-65844"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-65842"},"products":["n/a"],"published":"2025-12-03","related":[{"cvss_score":6.2,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-65841","kev_date_added":null,"published":"2025-12-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-03","vendors":["n/a"]},"summary":"Local attackers can exploit insecure symlink handling in support archive generation to read or modify arbitrary files, potentially exposing root-owned data.","url":"https://insights.sbomify.com/CVE-2025-65843/"}