CVE-2023-5369: copy_file_range insufficient capability rights check
Vendor fix available · Affected: FreeBSD · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 9% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
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. This 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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- FreeBSD · FreeBSDfrom 13.2-RELEASE before p4
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- FreeBSD
- Published
- October 2023
CoverageNo articles yet
No CyberSIXT article names CVE-2023-5369 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.