{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25578 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-25578 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25578 is a medium-severity vulnerability in Freebsd Freebsd, published on 26 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25578 and fix it if it is affected.\n\nWhat it is: CVE-2020-25578 is a medium-severity vulnerability in Freebsd Freebsd, published on 26 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-25578 in the wild and no public exploit code.\n\nAffected product: Freebsd Freebsd. 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-25578/ (Markdown: https://insights.sbomify.com/CVE-2020-25578/index.md)","id":"CVE-2020-25578","markdown":"https://insights.sbomify.com/CVE-2020-25578/index.md","name":"CVE-2020-25578","record":{"aliases":["GHSA-v45v-x46m-37q7"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"FreeBSD kernel","requires_auth":"none","summary":"Local attackers can read uninitialized kernel stack bytes via specific file systems, potentially leaking sensitive information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"freebsd","cpe":[{"product":"freebsd","vendor":"freebsd"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-665","name":"Improper Initialization"}],"description":"In FreeBSD 12.2-STABLE before r368969, 11.4-STABLE before r369047, 12.2-RELEASE before p3, 12.1-RELEASE before p13 and 11.4-RELEASE before p7 several file systems were not properly initializing the d_off field of the dirent structures returned by VOP_READDIR. In particular, tmpfs(5), smbfs(5), autofs(5) and mqueuefs(5) were failing to do so. As a result, eight uninitialized kernel stack bytes may be leaked to userspace by these file systems.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-12-05","github_poc":1,"max_poc_stars":7,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-12-05T04:39:04Z","kind":"github_poc","ref":"https://github.com/farazsth98/freebsd-dirent-info-leak-bugs","stars":7,"title":"CVE-2020-25578 and CVE-2020-25579: Some FreeBSD info leak bugs I found in 2020."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in FreeBSD","id":"CVE-2020-25578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"freebsd:freebsd","products":["freebsd:freebsd"],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in FreeBSD","id":"CVE-2020-25579"},"packages":[],"prev":{"headline":"Memory corruption in FreeBSD","id":"CVE-2020-25577"},"products":["FreeBSD"],"published":"2021-03-26","related":[{"cvss_score":10,"headline":"Memory corruption in FreeBSD","id":"CVE-2018-17160","kev_date_added":null,"published":"2018-12-04"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2014-3954","kev_date_added":null,"published":"2014-10-27"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2006-4304","kev_date_added":null,"published":"2006-08-24"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2006-0226","kev_date_added":null,"published":"2006-01-19"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2004-0002","kev_date_added":null,"published":"2004-02-03"},{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2001-0969","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2001-0388","kev_date_added":null,"published":"2001-09-18"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Local attackers can read uninitialized kernel stack bytes via specific file systems, potentially leaking sensitive information.","url":"https://insights.sbomify.com/CVE-2020-25578/"}