# CVE-2024-31695: Auth bypass in n/a

> Attackers can bypass fingerprint authentication when adding a new fingerprint in the Binance mobile application, potentially compromising account security.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2024
- **Updated:** 3 Dec 2024
- **Also known as:** GHSA-j8fr-cp65-m9m7

## What is CVE-2024-31695?

CVE-2024-31695 is a critical authentication bypass vulnerability in n/a, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A misconfiguration in the fingerprint authentication mechanism of Binance: BTC, Crypto and NFTS v2.85.4, allows attackers to bypass authentication when adding a new fingerprint.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-31695?


## How do I fix CVE-2024-31695?

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

## Is CVE-2024-31695 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31695 and fix it if it is affected.

What it is: CVE-2024-31695 is a critical authentication bypass vulnerability in n/a, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31695 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-2024-31695/ (Markdown: https://insights.sbomify.com/CVE-2024-31695/index.md)
```

## Sources

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

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