FirefoxWeb browser · Mozilla

CVE-2024-11702

HIGH · 7.5 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 133.0 or later.
See remediation →
84/100
Remediation priority · High
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
Copying sensitive information from Private Browsing tabs on Android, such as passwords, may have inadvertently stored data in the cloud-based clipboard history if enabled. This vulnerability affects Firefox < 133 and Thunderbird < 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 and Thunderbird versions prior to 133 could inadvertently sync sensitive data copied from Private Browsing tabs (such as passwords) to cloud-based clipboard history, bypassing the privacy protections expected of Private Browsing mode. This occurs when the cloud-based clipboard history feature is enabled, causing sensitive data to be persistently stored outside the Private Browsing session.

MitigationUpgrade Firefox and Thunderbird to version 133 or later on Android devices. Alternatively, disable cloud-based clipboard history in browser settings on Android to prevent sensitive Private Browsing data from being synced.

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
ThunderbirdApplication
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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify the product and platform
    Confirm you are using Mozilla Firefox or Thunderbird on an Android device. This vulnerability only affects the Android versions of these products.
    Affected if Not applicable - this is a prerequisite check
  2. Check the installed version
    Open the app, go to Settings > About [Firefox/Thunderbird] to view the current version number. Compare this against the affected range (versions prior to 133.0).
    Affected if The installed version is Firefox < 133.0 or Thunderbird < 133.0 on Android
  3. Verify cloud-based clipboard history status
    Navigate to Settings > Privacy & Security > Sync > Cloud-based clipboard history (or Settings > Privacy > Clipboard > Cloud history, depending on UI). Determine whether the cloud clipboard history feature is enabled.
    Affected if Cloud-based clipboard history is enabled in the browser settings

You are affected if you are running Firefox or Thunderbird version below 133.0 on Android AND have cloud-based clipboard history enabled, as sensitive data copied in Private Browsing mode could be synced to cloud storage.

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 and Thunderbird to version 133 or later on Android devices. Alternatively, disable cloud-based clipboard history in browser settings on Android to prevent sensitive Private Browsing data from being synced.

Recommended fix High confidence

Firefox 133.0 or Thunderbird 133.0

  1. Update Firefox to version 133.0 or later on Android
  2. Update Thunderbird to version 133.0 or later
  3. Restart the application after updating

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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