dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-31682

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-03
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
Incorrect access control in the fingerprint authentication mechanism of Phone Cleaner: Boost & Clean v2.2.0 allows attackers to bypass fingerprint authentication due to the use of a deprecated API.

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

The Phone Cleaner: Boost & Clean v2.2.0 Android application uses a deprecated fingerprint authentication API that fails to properly enforce biometric access controls, allowing attackers to bypass the fingerprint check entirely and gain unauthorized access to the application's cleaning and optimization features.

MitigationReplace the deprecated biometric authentication API with the current AndroidX Biometric API (androidx.biometric.BiometricPrompt) which properly validates biometric credentials and enforces authentication challenges.

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. Confirm app installation
    Go to Settings > Apps and search for 'Phone Cleaner: Boost & Clean' or check your app drawer for the app icon
    Affected if The app is present on the device
  2. Check installed version
    In Settings > Apps > Phone Cleaner: Boost & Clean, view the Version or App info field. Compare against v2.2.0
    Affected if Version shown is exactly 2.2.0
  3. Verify biometric authentication is enabled
    Open the app, go to Settings or Security settings within the app, and check if Fingerprint or Biometric authentication is turned on for app access
    Affected if Fingerprint/biometric lock is enabled in the app settings
  4. Check for deprecated FingerprintManager API
    Decompile the APK (using apktool or similar) and inspect the smali or Java code for imports or usage of 'android.hardware.fingerprint.FingerprintManager' instead of 'androidx.biometric.BiometricPrompt'
    Affected if Code contains references to the deprecated FingerprintManager API

If the Phone Cleaner: Boost & Clean app version is 2.2.0 and has fingerprint authentication enabled, the device is affected by this vulnerability.

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

Replace the deprecated biometric authentication API with the current AndroidX Biometric API (androidx.biometric.BiometricPrompt) which properly validates biometric credentials and enforces authentication challenges.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31682 — 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-31682 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