# CVE-2018-12445: Auth bypass in n/a

> Attackers can bypass biometric authentication in the Dropbox Android app by manipulating callback methods, potentially gaining unauthorized account access.

- **Severity:** Low 3.1 (`CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A: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:** 20 Jun 2018
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-8vf4-47vh-64rm

## What is CVE-2018-12445?

CVE-2018-12445 is a low-severity authentication bypass vulnerability in n/a, published on 20 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the com.dropbox.android application 98.2.2 for Android. The FingerprintManager class for Biometric validation allows authentication bypass through the callback method from onAuthenticationFailed to onAuthenticationSucceeded with null, because the fingerprint API in conjunction with the Android keyGenerator class is not implemented. In other words, an attacker could authenticate with an arbitrary fingerprint. NOTE: the vendor indicates that this is not an attack of interest within the context of their threat model, which excludes Android devices on which rooting has occurred

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-12445?

It affects 1 product.


Products: Dropbox Dropbox.

## How do I fix CVE-2018-12445?

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

## Is CVE-2018-12445 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12171](https://insights.sbomify.com/CVE-2019-12171/): Information disclosure in n/a (high 7.8)
- [CVE-2010-3354](https://insights.sbomify.com/CVE-2010-3354/): Path traversal in n/a (medium 6.9)
- [CVE-2018-12271](https://insights.sbomify.com/CVE-2018-12271/): Auth bypass in n/a (medium 6.4)
- [CVE-2018-12446](https://insights.sbomify.com/CVE-2018-12446/): Auth bypass in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12445 and fix it if it is affected.

What it is: CVE-2018-12445 is a low-severity authentication bypass vulnerability in n/a, published on 20 Jun 2018. 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-2018-12445 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-2018-12445/ (Markdown: https://insights.sbomify.com/CVE-2018-12445/index.md)
```

## Sources

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

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