CVE-2024-8897
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 · uneditedUnder certain conditions, an attacker with the ability to redirect users to a malicious site via an open redirect on a trusted site, may be able to spoof the address bar contents. This can lead to a malicious site to appear to have the same URL as the trusted site. *This bug only affects Firefox for Android. Other versions of Firefox are unaffected.* This vulnerability affects Firefox for Android < 130.0.1.
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 for Android contains an address bar spoofing vulnerability where an attacker leveraging an open redirect on a trusted site can manipulate the browser to display a trusted URL while actually navigating to a malicious site. This occurs due to improper handling of redirects in the address bar rendering logic on Android.
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< 130.0.1CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm Firefox for Android is installedIdentify the specific Firefox application on the Android device. Check the app information in Settings > Apps, looking for Firefox with package identifier 'org.mozilla.firefox'. This vulnerability affects only Firefox for Android, not Firefox for iOS, Firefox Focus, or desktop Firefox.Affected if The installed application is not Firefox for Android (the CVE specifically targets the Android implementation)
-
Check Firefox for Android version numberOpen Firefox for Android, tap the three-dot menu, select Settings, scroll to Help, then tap About Firefox. Note the version number displayed and compare it against 130.0.1.Affected if The installed version is earlier than 130.0.1 (versions prior to this release contain the vulnerability)
-
Assess open redirect exposureReview trusted websites frequently visited for open redirect vulnerabilities. Test whether URLs on trusted domains can be manipulated through redirect parameters to display one address in the browser while actually loading different content.Affected if An open redirect exists on a trusted domain AND the address bar displays the trusted URL while the browser navigates to an untrusted destination
The environment is affected if Firefox for Android with a version below 130.0.1 is in use and an attacker can leverage an open redirect on a trusted site to spoof the address bar display.
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 · scoped130.0.1
Upgrade Firefox for Android to version 130.0.1 or later to patch the address bar spoofing vulnerability.
Firefox for Android 130.0.1
- Open the Firefox for Android application on your device
- Tap the menu button (three dots or 'More' option)
- Navigate to Settings
- Scroll down and tap on 'Firefox Updates' or 'About Firefox'
- Tap 'Check for updates' or allow the app to check automatically
- If an update is available, tap 'Update' to install Firefox for Android version 130.0.1 or later
- Alternatively, open the Google Play Store, search for 'Firefox', and tap 'Update' on the Firefox for Android listing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8897 — 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-8897 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