dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-22758

HIGH · 8.8 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 97.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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
When clicking on a tel: link, USSD codes, specified after a <code>\*</code> character, would be included in the phone number. On certain phones, or on certain carriers, if the number was dialed this could perform actions on a user's account, similar to a cross-site request forgery attack.<br>*This bug only affects Firefox for Android. Other operating systems are unaffected.*. This vulnerability affects Firefox < 97.

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

Firefox for Android fails to properly sanitize tel: links, allowing USSD codes (strings beginning with * and ending with #) to be passed through to the phone dialer. Attackers can embed malicious USSD codes in tel: links that, when clicked, trigger carrier operations like balance transfers, call forwarding, or account modifications without user consent.

MitigationUpgrade Firefox for Android to version 97 or later to receive the patch that properly sanitizes tel: link payloads.

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:< 97.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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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
    Open Android Settings > Apps and look for 'Firefox' (the main browser app, not Firefox Focus or Firefox Preview). The vulnerable component is specifically the Firefox for Android browser.
    Affected if The app 'Firefox' by Mozilla is installed on the device.
  2. Check the Firefox for Android version
    Open Firefox for Android, tap the three-dot menu > Settings > About Firefox. The version number is displayed at the top.
    Affected if The displayed version number is below 97.0 (for example, 96.x, 95.x, etc.).
  3. Verify tel: link handling is enabled
    In Firefox for Android, go to Settings > Advanced > Open links in apps. Ensure 'Open links in apps' is checked, which allows tel: links to be passed to the phone dialer.
    Affected if 'Open links in apps' is enabled (this is the default setting, making tel: links clickable and functional).

You are affected if Firefox for Android version is below 97.0 and tel: link handling is enabled, as malicious tel: links with USSD codes could execute carrier commands without user consent.

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

Upgrade Firefox for Android to version 97 or later to receive the patch that properly sanitizes tel: link payloads.

Recommended fix High confidence

Firefox 97.0 or later for Android

  1. Check the current Firefox for Android version in Settings > Firefox > Version
  2. Open Google Play Store and search for Firefox
  3. Update Firefox to version 97.0 or later
  4. Alternatively, enable auto-updates in Firefox settings to receive future security updates automatically
  5. Verify the update was successful by checking the version number in Settings > Firefox > Version
Caveat No breaking changes expected - this is a security update with no functional modifications to the browser

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-2022-22758 — 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-2022-22758 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