FirefoxWeb browser · Mozilla
CVE-2024-6605
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 · uneditedFirefox Android allowed immediate interaction with permission prompts. This could be used for tapjacking. This vulnerability affects Firefox < 128.
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 · high confidenceFirefox Android had a vulnerability where permission prompts could be interacted with immediately after display, enabling tapjacking attacks where a malicious app could overlay or intercept user interactions with system permission dialogs.
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
FirefoxWeb browser
< 128.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate Firefox Android installationOpen the device Settings app, go to Apps or Applications, and search for 'Firefox' or 'Mozilla Firefox' in the installed applications list.Affected if Firefox Android is not found on the device, this CVE does not apply.
-
Identify the installed Firefox Android versionIn the device Settings > Apps > Firefox (or Mozilla Firefox), look for the 'Version' or 'App info' field displaying the current version number.Affected if Unable to determine the version number from the app info screen.
-
Compare version against affected rangeTake the installed version number (for example, 127.x.x) and compare it to 128.0. Any version number less than 128.0 (such as 127.1, 127.0.1, or 126.x) falls within the affected range.Affected if The installed version is 127.x or any version below 128.0, meaning the device is affected by this tapjacking vulnerability.
-
Confirm Android as the target platformVerify that the vulnerable app is Firefox for Android (the mobile app), not Firefox for desktop or Firefox iOS.Affected if The affected product is specifically Firefox for Android; other Firefox versions are not impacted by this CVE.
A device is affected if Firefox Android version 127.x or lower is installed, as the permission prompt timing vulnerability exists in versions below 128.0.
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 · scoped128.0
Update Firefox for Android to version 128 or later to receive the fix for this tapjacking vulnerability in permission prompts.
Firefox Android 128.0
- Open the Google Play Store on your Android device
- Search for "Firefox" or "Firefox Browser"
- Tap on the Firefox app
- If an update is available, tap "Update" to install Firefox 128.0 or later
- Alternatively, enable automatic updates in the Play Store settings to ensure you receive future security updates
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6605 — 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-6605 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