{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-8058 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-8058 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-8058 is a high-severity path traversal vulnerability in Lenovo FileZ Client, published on 16 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-8058 and fix it if it is affected.\n\nWhat it is: CVE-2024-8058 is a high-severity path traversal vulnerability in Lenovo FileZ Client, published on 16 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-8058 in the wild and no public exploit code.\n\nAffected product: Lenovo FileZ Client. 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-2024-8058/ (Markdown: https://insights.sbomify.com/CVE-2024-8058/index.md)","id":"CVE-2024-8058","markdown":"https://insights.sbomify.com/CVE-2024-8058/index.md","name":"CVE-2024-8058","record":{"aliases":["GHSA-rpq3-9v7c-qwm4"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"FileZ Client","requires_auth":"none","summary":"An attacker can read arbitrary files on the device by placing a crafted file in the FileZ directory due to improper parsing.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"lenovo","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-1287","name":"Improper Validation of Specified Type of Input"}],"description":"An improper parsing vulnerability was reported in the FileZ client that could allow a crafted file in the FileZ directory to read arbitrary files on the device due to URL preloading.","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":"Path traversal in FileZ Client","id":"CVE-2024-8058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in HX Enclosure Certified Node (ThinkAgile) XCC","id":"CVE-2024-8059"},"packages":[],"prev":{"headline":"Improper Access Control in danswer-ai/danswer","id":"CVE-2024-8057"},"products":["FileZ Client"],"published":"2024-12-16","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-08-27","vendors":["Lenovo"]},"summary":"An attacker can read arbitrary files on the device by placing a crafted file in the FileZ directory due to improper parsing.","url":"https://insights.sbomify.com/CVE-2024-8058/"}