Arbitrary file access via missing seek check
Published Oct 4, 2023 · Updated Feb 13, 2025
Improper privilege checking in FreeBSD 13.2-RELEASE before p4 allows local users to read or write arbitrary file locations. The copy_file_range system call accepts explicit offsets after checking only CAP_READ on the input descriptor and CAP_WRITE on the output descriptor, without requiring CAP_SEEK. Exploitation requires a sandboxed process to hold a descriptor with read or write rights but no seek right, limiting access to arbitrary locations within that descriptor's file.
Summary
What happened
Improper privilege checking in FreeBSD 13.2-RELEASE before p4 allows local users to read or write arbitrary file locations. The copy_file_range system call accepts explicit offsets after checking only CAP_READ on the input descriptor and CAP_WRITE on the output descriptor, without requiring CAP_SEEK. Exploitation requires a sandboxed process to hold a descriptor with read or write rights but no seek right, limiting access to arbitrary locations within that descriptor's file.
The record
- CVE
- CVE-2023-5369
- Published
- Oct 4, 2023
- Updated
- Feb 13, 2025
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-273, T1565.001, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13.2-RELEASE <p4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo