# CVE-2020-36250: Security feature bypass in n/a

> Attackers can bypass the ownCloud Android app's lock screen by manipulating the system date, potentially exposing protected data.

- **Severity:** Medium 6.1 (`CVSS:3.1/AC:L/AV:P/A:N/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8ph5-68pq-3fm9

## What is CVE-2020-36250?

CVE-2020-36250 is a medium-severity vulnerability in n/a, published on 19 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the ownCloud application before 2.15 for Android, the lock protection mechanism can be bypassed by moving the system date/time into the past.

## Which versions are affected by CVE-2020-36250?

It affects 1 product.


Products: Owncloud Owncloud Client.

## How do I fix CVE-2020-36250?

No fix has been published for CVE-2020-36250 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36250 being exploited?

There is no known exploitation of CVE-2020-36250 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-25338](https://insights.sbomify.com/CVE-2022-25338/): Missing authorization in n/a (medium 6.8)
- [CVE-2023-23948](https://insights.sbomify.com/CVE-2023-23948/): ownCloud Android app vulnerable to SQL Injection (medium 6.2)
- [CVE-2022-25339](https://insights.sbomify.com/CVE-2022-25339/): Missing authorization in n/a (medium 5.5)
- [CVE-2023-24804](https://insights.sbomify.com/CVE-2023-24804/): ownCloud Android app vulnerable to Path Traversal (medium 5.0)
- [CVE-2015-5955](https://insights.sbomify.com/CVE-2015-5955/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36250 and fix it if it is affected.

What it is: CVE-2020-36250 is a medium-severity vulnerability in n/a, published on 19 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36250 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36250/ (Markdown: https://insights.sbomify.com/CVE-2020-36250/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36250
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36250
- OSV: https://osv.dev/vulnerability/CVE-2020-36250

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36250/
Summaries are generated and may contain mistakes; the official description above is the record.