{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-0001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0001 is a medium-severity path traversal vulnerability in Abacus, published on 17 Feb 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-0001 and fix it if it is affected.\n\nWhat it is: CVE-2025-0001 is a medium-severity path traversal vulnerability in Abacus, published on 17 Feb 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-0001 in the wild and no public exploit code.\n\nAffected product: Abacus. 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-0001/ (Markdown: https://insights.sbomify.com/CVE-2025-0001/index.md)","id":"CVE-2025-0001","markdown":"https://insights.sbomify.com/CVE-2025-0001/index.md","name":"CVE-2025-0001","record":{"aliases":["GHSA-239v-3pc9-55cf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Abacus ERP","requires_auth":"low_privilege","summary":"Authenticated attackers can read arbitrary files from the Abacus ERP server, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-36","name":"Absolute Path Traversal"}],"description":"Abacus ERP is versions older than 2024.210.16036, 2023.205.15833, 2022.105.15542 are affected by an authenticated arbitrary file read vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"authenticated arbitrary file read vulnerability","id":"CVE-2025-0001","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":"Use after free in Xilinx Run Time (XRT)","id":"CVE-2025-0003"},"packages":[],"prev":{"headline":"llama.cpp before b3701 Out-of-Bounds Read in llama_decode via Token IDs","id":"CVE-2024-58400"},"products":["Abacus"],"published":"2025-02-17","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-02-18","vendors":["Abacus Research AG"]},"summary":"Authenticated attackers can read arbitrary files from the Abacus ERP server, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2025-0001/"}