Audit-trail bypass via unlogged handle-based file access
Published Mar 30, 2022 · Updated Aug 4, 2024
Audit-rule bypass in Linux Kernel through 5.17 allows local users with elevated privileges to access files without file-watch records. Path-based audit rules do not associate open_by_handle_at access with the watched pathname, so the audit subsystem omits the event. CAP_DAC_READ_SEARCH is required; the flaw hides activity from path watches but grants no additional file access.
Summary
What happened
Audit-rule bypass in Linux Kernel through 5.17 allows local users with elevated privileges to access files without file-watch records. Path-based audit rules do not associate open_by_handle_at access with the watched pathname, so the audit subsystem omits the event. CAP_DAC_READ_SEARCH is required; the flaw hides activity from path watches but grants no additional file access.
The record
- CVE
- CVE-2020-35501
- Published
- Mar 30, 2022
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-863
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 30, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=affecting all versions up to kernel 5.17
What conditions does exploitation require?
What is affected?
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