A wrong check for the system time in the Android App 3.9.0 causes a bypass of the lock protection when changing the time of the system to t…

published 2020-02-04 6y ago modified 2026-06-17 4mo ago also EUVD-2019-6572

cvss: 6.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits: 0; none known

A wrong check for the system time in the Android App 3.9.0 causes a bypass of the lock protection when changing the time of the system to the past.

Is CVE-2019-15615 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.1	CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	3.6	AV:L/AC:L/Au:N/C:P/I:P/A:N

Affected products

n/a Nextcloud Android

Classification

Weakness

CWE-284 Improper Access Control
CWE-287 Improper Authentication

References

hackerone.com /reports/747726
third-party-advisory
nextcloud.com /security/advisory/?id=NC-SA-2020-004
permissions-required

Sources

CVE List CVE-2019-15615
NVD CVE-2019-15615

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.