{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5369 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5369 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5369 is a high-severity vulnerability in Freebsd Freebsd, published on 4 Oct 2023. 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-2023-5369 and fix it if it is affected.\n\nWhat it is: CVE-2023-5369 is a high-severity vulnerability in Freebsd Freebsd, published on 4 Oct 2023. 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-2023-5369 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-2023-5369/ (Markdown: https://insights.sbomify.com/CVE-2023-5369/index.md)","id":"CVE-2023-5369","markdown":"https://insights.sbomify.com/CVE-2023-5369/index.md","name":"CVE-2023-5369","record":{"aliases":["GHSA-4hwj-mwvm-vc26"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"FreeBSD kernel","requires_auth":"low_privilege","summary":"Sandboxed processes can bypass seek restrictions to read or write arbitrary file locations via the copy_file_range system call.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"freebsd","cpe":[{"product":"freebsd","vendor":"freebsd"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-273","name":"Improper Check for Dropped Privileges"}],"description":"Before correction, the copy_file_range system call checked only for the CAP_READ and CAP_WRITE capabilities on the input and output file descriptors, respectively.  Using an offset is logically equivalent to seeking, and the system call must additionally require the CAP_SEEK capability.\n\nThis incorrect privilege check enabled sandboxed processes with only read or write but no seek capability on a file descriptor to read data from or write data to an arbitrary location within the file corresponding to that file descriptor.","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":"copy_file_range insufficient capability rights check","id":"CVE-2023-5369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"freebsd:freebsd","products":["freebsd:freebsd"],"type":"privilege_escalation","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"arm64 boot CPUs may lack speculative execution protections","id":"CVE-2023-5370"},"packages":[],"prev":{"headline":"msdosfs data disclosure","id":"CVE-2023-5368"},"products":["FreeBSD"],"published":"2023-10-04","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["FreeBSD"]},"summary":"Sandboxed processes can bypass seek restrictions to read or write arbitrary file locations via the copy_file_range system call.","url":"https://insights.sbomify.com/CVE-2023-5369/"}