Cache file overwrite via unsanitized document filename
Published Jan 29, 2025 · Updated Feb 12, 2025
Relative path traversal in Google file_selector_android 0.5.1 through 0.5.1+11 allows local users to overwrite app cache files. The getPathFromCopyOfFileFromUri flow trusts a document provider's DISPLAY_NAME when constructing the cache destination, without neutralizing relative path segments. Exploitation requires a malicious document provider to be installed and the user to select its crafted file, limiting writes to files reachable from the app's cache path.
Summary
What happened
Relative path traversal in Google file_selector_android 0.5.1 through 0.5.1+11 allows local users to overwrite app cache files. The getPathFromCopyOfFileFromUri flow trusts a document provider's DISPLAY_NAME when constructing the cache destination, without neutralizing relative path segments. Exploitation requires a malicious document provider to be installed and the user to select its crafted file, limiting writes to files reachable from the app's cache path.
The record
- CVE
- CVE-2024-54461
- Published
- Jan 29, 2025
- Updated
- Feb 12, 2025
- Vendor
- Product
- file_selector_android
- Classifications
- CWE-23
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 29, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 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=0.5.1 <=0.5.1+11
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