Vulnerability 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. 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Freebsd | Freebsd | 13.2 |
Related Weaknesses (CWE)
References
- https://security.FreeBSD.org/advisories/FreeBSD-SA-23:13.capsicum.ascVendor Advisory
- https://security.netapp.com/advisory/ntap-20231124-0009/
- https://security.FreeBSD.org/advisories/FreeBSD-SA-23:13.capsicum.ascVendor Advisory
- https://security.netapp.com/advisory/ntap-20231124-0009/
FAQ
What is CVE-2023-5369?
CVE-2023-5369 is a vulnerability with a CVSS score of 7.1 (HIGH). 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 equiva...
How severe is CVE-2023-5369?
CVE-2023-5369 has been rated HIGH with a CVSS base score of 7.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2023-5369?
Check the references section above for vendor advisories and patch information. Affected products include: Freebsd Freebsd.