Local file existence disclosure via path traversal
Published Jun 8, 2020 · Updated Aug 4, 2024
Incorrect authorization in LinuxTV xawtv before 3.107 allows local users to probe arbitrary file existence through setuid-root v4l-conf. The dev_open() function accepts paths beginning with /dev/ without resolving relative components, then invokes stat(), open(O_RDWR), and fstat() on unintended paths. Exploitation requires local access to a setuid-root v4l-conf installation; differing errors disclose file existence, while the privileged open does not expose file contents.
Summary
What happened
Incorrect authorization in LinuxTV xawtv before 3.107 allows local users to probe arbitrary file existence through setuid-root v4l-conf. The dev_open() function accepts paths beginning with /dev/ without resolving relative components, then invokes stat(), open(O_RDWR), and fstat() on unintended paths. Exploitation requires local access to a setuid-root v4l-conf installation; differing errors disclose file existence, while the privileged open does not expose file contents.
The record
- CVE
- CVE-2020-13696
- Published
- Jun 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1083
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- v4l-conf relative-path proof of conceptproof of concept · demonstrated
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