dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-31695

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A misconfiguration in the fingerprint authentication mechanism of the Binance mobile app v2.85.4 allows attackers to bypass authentication during the new fingerprint enrollment process, enabling unauthorized access to the application.

MitigationUpdate to the patched version of Binance: BTC, Crypto and NFTS as soon as available; review and properly configure biometric authentication flows to ensure proper validation during fingerprint enrollment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed Binance app version
    On Android: Go to Settings > Apps > Binance > App info > Version. On iOS: Go to Settings > Binance > Version. Compare the version number to v2.85.4.
    Affected if The installed version is v2.85.4 exactly.
  2. Verify if biometric authentication is enabled
    Open the Binance app, go to Settings > Security > Biometric Authentication (or Fingerprint/Face ID). Check if any biometric option is toggled on or configured.
    Affected if Biometric authentication is enabled on the vulnerable version.
  3. Check for recent fingerprint enrollment activity
    Review the app's security logs or authentication history if available. Look for any fingerprint enrollment events, especially if multiple fingerprints were added unexpectedly.
    Affected if New fingerprint enrollment occurred without the user's explicit action.
  4. Verify account access without authentication
    Attempt to access the Binance app after closing it completely. If the app allows access without prompting for authentication when fingerprint is set up, this may indicate the bypass.
    Affected if The app grants access without requiring fingerprint authentication after a fresh launch.

You are affected if the Binance mobile app version is v2.85.4 and fingerprint/biometric authentication is enabled or was recently enrolled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the patched version of Binance: BTC, Crypto and NFTS as soon as available; review and properly configure biometric authentication flows to ensure proper validation during fingerprint enrollment.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31695 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-31695 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data