Physical authentication bypass via mishandled fingerprint enrollment
Published Nov 14, 2024 · Updated Dec 3, 2024
Incorrect authorization in Binance 2.85.4 allows physically proximate attackers to bypass fingerprint authentication via enrollment. The Android app fails to invalidate its fingerprint-lock protection or require account reauthentication after a new device fingerprint is enrolled. Physical possession and knowledge of the device lock-screen PIN are required; successful bypass exposes financial information and transaction functions.
Summary
What happened
Incorrect authorization in Binance 2.85.4 allows physically proximate attackers to bypass fingerprint authentication via enrollment. The Android app fails to invalidate its fingerprint-lock protection or require account reauthentication after a new device fingerprint is enrolled. Physical possession and knowledge of the device lock-screen PIN are required; successful bypass exposes financial information and transaction functions.
The record
- CVE
- CVE-2024-31695
- Published
- Nov 14, 2024
- Updated
- Dec 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1556
- Attack vector
- physical
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 14, 2024CVE publishedPublication date reported by the CVE source.
- Dec 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo