Lock protection bypass via system time rollback
Published Feb 4, 2020 · Updated Aug 5, 2024
Improper authentication in Nextcloud Android app 3.9.0 allows attackers to bypass lock protection by setting the device clock to the past. The lock-check logic accepts a rolled-back system time, so the passcode gate is skipped. Physical access to the device is required, after which attackers can access and modify protected files through the client.
Summary
What happened
Improper authentication in Nextcloud Android app 3.9.0 allows attackers to bypass lock protection by setting the device clock to the past. The lock-check logic accepts a rolled-back system time, so the passcode gate is skipped. Physical access to the device is required, after which attackers can access and modify protected files through the client.
The record
- CVE
- CVE-2019-15615
- Published
- Feb 4, 2020
- Updated
- Aug 5, 2024
- Vendor
- Nextcloud GmbH
- Product
- Nextcloud Android app
- Classifications
- CWE-284, CWE-287
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=3.9.1
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.
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