FirefoxWeb browser · Mozilla

CVE-2024-11703

MEDIUM · 5.7 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 133.0 or later.
See remediation →
57/100
Remediation priority · Elevated

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
On Android, Firefox may have inadvertently allowed viewing saved passwords without the required device PIN authentication. This vulnerability affects Firefox < 133.

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

On Android, Firefox's password manager failed to properly enforce device PIN authentication before allowing users to view saved passwords, bypassing a security control intended to protect sensitive credential data. This affects Firefox versions prior to 133 on Android devices.

MitigationUpgrade Firefox to version 133 or later on all Android devices to ensure device PIN authentication is properly required before accessing saved passwords.

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:< 133.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
Physical
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:P/AC:L/PR:L/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 device is Android
    Check if the device is running Android by going to Settings > About Phone > Android version
    Affected if Device is not Android - not affected by this CVE on Android
  2. Check Firefox version on Android
    Open Firefox app > tap the three-dot menu > Settings > scroll down and tap Firefox > check the Version number displayed
    Affected if Version shown is below 133.0 (for example, 132.x, 132.0, 131.x, etc.)
  3. Confirm password manager feature is in use
    Go to Firefox Settings > Logins and Passwords (or Saved Logins) to confirm the password manager feature is accessible
    Affected if Password manager is accessible on a vulnerable Firefox version

User is affected if Firefox version is below 133.0 on an Android device and the password manager feature is accessible without proper PIN authentication enforcement

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

Upgrade Firefox to version 133 or later on all Android devices to ensure device PIN authentication is properly required before accessing saved passwords.

Recommended fix High confidence

Firefox 133.0 for Android

  1. Open the Google Play Store app on your Android device
  2. Search for 'Firefox' or 'Mozilla Firefox'
  3. Locate the Firefox browser app in the search results
  4. Tap the 'Update' button to install Firefox 133.0 or later
  5. Alternatively, ensure automatic updates are enabled in the Play Store settings to receive future security updates
Caveat Standard upgrade risk - verify compatibility with any browser extensions or enterprise policies in use

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11703 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