dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-4765

HIGH · 8.1 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 126.0 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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
Web application manifests were stored by using an insecure MD5 hash which allowed for a hash collision to overwrite another application's manifest. This could have been exploited to run arbitrary code in another application's context. *This issue only affects Firefox for Android. Other versions of Firefox are unaffected.* This vulnerability affects Firefox < 126.

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 confidence

In Firefox for Android versions prior to 126, web application manifests were stored using MD5 hashing, which is cryptographically broken and vulnerable to hash collision attacks. An attacker could craft a malicious manifest that collides with a legitimate application's manifest hash, causing the browser to overwrite the original manifest and execute arbitrary code in another application's context.

MitigationUpdate Firefox for Android to version 126 or later. For organizations, deploy the update via mobile device management or ensure end users update through the Google Play Store.

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
Affected:< 126.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm you are using Firefox for Android
    Check that the affected application is Firefox for Android (the mobile app), not Firefox Desktop or Firefox iOS. This vulnerability only affects the Android version.
    Affected if Using any version of Firefox other than Firefox for Android (the vulnerability does not apply to desktop or iOS)
  2. Check Firefox for Android version
    Open Firefox for Android, tap the three-dot menu, go to Settings > About Firefox. The version number is displayed on this page. Alternatively, navigate to about:config in the address bar and look for the version entry.
    Affected if Version is prior to 126.0 (versions 125.x and earlier are affected)
  3. Determine if any web apps or PWAs are installed
    Open Firefox for Android and look for any installed web apps in the app menu or home screen shortcuts. These are Progressive Web Apps (PWAs) that were installed by tapping 'Add to Home screen' or similar functionality.
    Affected if No web apps/PWAs are installed means the manifest storage vulnerability has no target, even on vulnerable versions

You are affected if you use Firefox for Android with a version prior to 126.0 AND have installed one or more web applications/PWAs, as these are what use the vulnerable MD5 manifest storage mechanism.

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.

dbcve · scoped
Upgrade available Upgrade to 126.0 or later
Fixed in 126.0
Interim mitigation

Update Firefox for Android to version 126 or later. For organizations, deploy the update via mobile device management or ensure end users update through the Google Play Store.

Recommended fix High confidence

Firefox 126.0 (Android)

  1. Open the Google Play Store on your Android device
  2. Search for "Firefox" or "Mozilla Firefox"
  3. Tap on the Firefox app and check if an update is available
  4. If an update is available, tap "Update" to install Firefox 126.0 or later
  5. Alternatively, enable auto-updates in the Play Store to ensure you receive future security updates
  6. After updating, verify the version by going to Firefox > Settings > About Firefox - it should show version 126.0 or higher
Caveat No major breaking changes expected; this is a security update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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