# CVE-2020-8791: Missing authorization in n/a

> Remote attackers can exploit IDOR in the OKLOK app to harvest sensitive user data and take over accounts by guessing user IDs.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fgmr-rcwc-wh2p

## What is CVE-2020-8791?

CVE-2020-8791 is a medium-severity missing authorization vulnerability in n/a, published on 4 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The OKLOK (3.1.1) mobile companion app for Fingerprint Bluetooth Padlock FB50 (2.3) allows remote attackers to submit API requests using authenticated but unauthorized tokens, resulting in IDOR issues. A remote attacker can use their own token to make unauthorized API requests on behalf of arbitrary user IDs. Valid and current user IDs are trivial to guess because of the user ID assignment convention used by the app. A remote attacker could harvest email addresses, unsalted MD5 password hashes, owner-assigned lock names, and owner-assigned fingerprint names for any range of arbitrary user IDs.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Oklok Project Oklok.

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

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

## Is CVE-2020-8791 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-8790](https://insights.sbomify.com/CVE-2020-8790/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-10876](https://insights.sbomify.com/CVE-2020-10876/): Auth bypass in n/a (high 7.5)
- [CVE-2020-8792](https://insights.sbomify.com/CVE-2020-8792/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8791 is a medium-severity missing authorization vulnerability in n/a, published on 4 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8791 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-8791/ (Markdown: https://insights.sbomify.com/CVE-2020-8791/index.md)
```

## Sources

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

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