{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-6108 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-6108 is a high-severity memory corruption vulnerability in F2fs-Tools, published on 15 Oct 2020. 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-2020-6108 and fix it if it is affected.\n\nWhat it is: CVE-2020-6108 is a high-severity memory corruption vulnerability in F2fs-Tools, published on 15 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-6108 in the wild and no public exploit code.\n\nAffected product: F2fs-Tools. 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-2020-6108/ (Markdown: https://insights.sbomify.com/CVE-2020-6108/index.md)","id":"CVE-2020-6108","markdown":"https://insights.sbomify.com/CVE-2020-6108/index.md","name":"CVE-2020-6108","record":{"aliases":["ALPINE-CVE-2020-6108","DEBIAN-CVE-2020-6108","GHSA-cf92-4fvh-jjvh","UBUNTU-CVE-2020-6108"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"F2fs filesystem tools","requires_auth":"high_privilege","summary":"A heap buffer overflow in F2fs-Tools allows attackers to execute arbitrary code by providing a maliciously crafted f2fs filesystem image.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"f2fs-tools","vendor":"f2fs-tools_project"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-131","name":"Incorrect Calculation of Buffer Size"}],"description":"An exploitable code execution vulnerability exists in the fsck_chk_orphan_node functionality of F2fs-Tools F2fs.Fsck 1.13. A specially crafted f2fs filesystem can cause a heap buffer overflow resulting in a code execution. An attacker can provide a malicious file to trigger this 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":true,"headline":"Memory corruption in F2fs-Tools","id":"CVE-2020-6108","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in Zoom","id":"CVE-2020-6109"},"packages":[],"prev":{"headline":"Information disclosure in F2fs-Tools","id":"CVE-2020-6107"},"products":["F2fs-Tools"],"published":"2020-10-15","related":[{"cvss_score":8.2,"headline":"Code injection in F2fs-Tools","id":"CVE-2020-6105","kev_date_added":null,"published":"2020-10-15"},{"cvss_score":6.7,"headline":"Memory corruption in F2fs-tools","id":"CVE-2020-6070","kev_date_added":null,"published":"2020-08-10"},{"cvss_score":4.4,"headline":"Information disclosure in F2FS-Tools","id":"CVE-2020-6104","kev_date_added":null,"published":"2020-10-15"},{"cvss_score":4.4,"headline":"Information disclosure in F2fs-Tools","id":"CVE-2020-6106","kev_date_added":null,"published":"2020-10-15"},{"cvss_score":4.4,"headline":"Information disclosure in F2fs-Tools","id":"CVE-2020-6107","kev_date_added":null,"published":"2020-10-15"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A heap buffer overflow in F2fs-Tools allows attackers to execute arbitrary code by providing a maliciously crafted f2fs filesystem image.","url":"https://insights.sbomify.com/CVE-2020-6108/"}