dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-9395

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-01
Fix available
A fix is available. Upgrade to 131.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
A specially crafted filename containing a large number of spaces could obscure the file's extension when displayed in the download dialog. *This bug only affects Firefox for Android. Other versions of Firefox are unaffected.* This vulnerability affects Firefox < 131.

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 before 131, a filename containing an excessive number of trailing spaces can cause the file extension to be hidden or obscured in the download dialog's displayed name. This UI misrepresentation could trick users into believing a potentially dangerous file (e.g., an executable) is a benign file type based on the visible extension.

MitigationUpdate Firefox for Android to version 131 or later to resolve this vulnerability. Users should also exercise caution with unexpected file downloads regardless of apparent file type.

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:< 131.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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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

  1. Confirm Firefox for Android is installed
    Check the device's installed applications list for Mozilla Firefox for Android. On Android, this can be viewed in Settings > Apps > Mozilla Firefox, or via adb shell pm list packages | grep mozilla
    Affected if Firefox for Android package is present on the device
  2. Retrieve the installed Firefox for Android version
    In Settings > Apps > Mozilla Firefox > App info, note the version number displayed. Alternatively, use adb shell dumpsys package org.mozilla.firefox | grep versionName
    Affected if A version number is returned from the package manager
  3. Compare version against affected range
    Compare the installed version number to the affected range: any version before 131.0 (e.g., 130.3, 130.0.3, 128.0.1) is affected
    Affected if Installed version is less than 131.0 (e.g., 130.x, 129.x, 128.x)
  4. Verify download dialog behavior (optional confirmation)
    If desired, download a file with a double extension (e.g., document.pdf.exe) containing trailing spaces in the filename and observe whether the download dialog correctly displays the full extension or truncates it
    Affected if The extension appears hidden or truncated in the download dialog due to trailing spaces

The user is affected if Firefox for Android is installed and the version is below 131.0, as the download dialog can obscure file extensions in filenames with excessive trailing spaces.

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 131.0 or later
Fixed in 131.0
Interim mitigation

Update Firefox for Android to version 131 or later to resolve this vulnerability. Users should also exercise caution with unexpected file downloads regardless of apparent file type.

Recommended fix High confidence

Firefox 131.0 for Android

  1. Open the Google Play Store app on your Android device
  2. Search for 'Firefox' or 'Mozilla Firefox'
  3. Tap on the Firefox app from Mozilla
  4. If an update is available, tap the 'Update' button. If not already installed, tap 'Install'
  5. Wait for the update/installation to complete
  6. Launch Firefox and verify the version is 131.0 or later by going to Menu > Settings > About Firefox

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-9395 — 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-9395 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