{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-6104 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-6104 is a medium-severity 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-6104 and fix it if it is affected.\n\nWhat it is: CVE-2020-6104 is a medium-severity 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-6104 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-6104/ (Markdown: https://insights.sbomify.com/CVE-2020-6104/index.md)","id":"CVE-2020-6104","markdown":"https://insights.sbomify.com/CVE-2020-6104/index.md","name":"CVE-2020-6104","record":{"aliases":["ALPINE-CVE-2020-6104","DEBIAN-CVE-2020-6104","GHSA-hjcj-jfhg-v58h","UBUNTU-CVE-2020-6104"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"F2FS filesystem tools","requires_auth":"high_privilege","summary":"An attacker can disclose sensitive information by providing a specially crafted F2FS filesystem image to the fsck utility.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"f2fs-tools","vendor":"f2fs-tools_project"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An exploitable information disclosure vulnerability exists in the get_dnode_of_data functionality of F2fs-Tools F2fs.Fsck 1.13. A specially crafted f2fs filesystem can cause information disclosure resulting in a information disclosure. 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":"Information disclosure in F2FS-Tools","id":"CVE-2020-6104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in F2fs-Tools","id":"CVE-2020-6105"},"packages":[],"prev":{"headline":"Memory corruption in AMD","id":"CVE-2020-6103"},"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":8.2,"headline":"Memory corruption in F2fs-Tools","id":"CVE-2020-6108","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-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":"An attacker can disclose sensitive information by providing a specially crafted F2FS filesystem image to the fsck utility.","url":"https://insights.sbomify.com/CVE-2020-6104/"}