CVE-2024-40672
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 · uneditedIn onCreate of ChooserActivity.java, there is a possible way to bypass factory reset protections due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
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 confidenceA missing permission check in the onCreate method of ChooserActivity.java in Android allows a local attacker to bypass factory reset protection (FRP) mechanisms. This enables privilege escalation without requiring additional execution privileges or user interaction, potentially allowing unauthorized device reset and takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.0= 12.1= 13.0= 14.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android version numberGo to Settings > About Phone > Android version (or Settings > System > Software version on some devices) and note the displayed versionAffected if The version shown is exactly 12.0, 12.1, 13.0, or 14.0
-
Verify build number matches affected releasesIn Settings > About Phone > Build number, confirm the build corresponds to Android 12, 12.1, 13, or 14 official releasesAffected if The build indicates Android 12, 12.1, 13, or 14 and the version matches the affected list
-
Confirm device has FRP protection enabledAfter a factory reset, observe if the device prompts for the previously associated Google account credentials before allowing full setup (this indicates FRP is active)Affected if FRP protection is present but the device allows bypassing this check through ChooserActivity exploitation
-
Check for unexpected account accessReview Settings > Accounts to see if a previously linked Google account is missing or if an unknown account has been added after a factory resetAffected if The device was factory reset and FRP was bypassed allowing unauthorized account access
The device is affected if it runs Android 12.0, 12.1, 13.0, or 14.0 and an unauthorized party could bypass Factory Reset Protection to gain access without the original account credentials.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply the security patch that adds proper permission validation in ChooserActivity.onCreate() to ensure factory reset protection checks are enforced before allowing reset operations.
Android 15 (API level 35) or September 2024 security patch level
- 1. Navigate to Settings > System > Software Update on the affected Android device
- 2. Check for and install the latest Android security patch level update
- 3. If available, upgrade the device to Android 15 (API level 35) which contains the fix for the missing permission check in ChooserActivity
- 4. Verify the device is running security patch level September 2024 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-40672 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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