FirefoxWeb browser · Mozilla
CVE-2022-36317
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 · uneditedWhen visiting a website with an overly long URL, the user interface would start to hang. Due to session restore, this could lead to a permanent Denial of Service.<br>*This bug only affects Firefox for Android. Other operating systems are unaffected.*. This vulnerability affects Firefox < 103.
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 confidenceFirefox for Android versions before 103 contains a denial-of-service vulnerability where an overly long URL causes the user interface to hang. Due to session restore functionality, this hang persists across browser restarts, creating a permanent DoS condition.
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
< 103.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Firefox for Android is installedCheck the device for the Firefox for Android application in the app drawer or via 'adb shell pm list packages | grep firefox'Affected if Firefox for Android is present on the device
-
Determine the installed Firefox for Android versionOpen the Play Store app listing for Firefox, check the app info screen, or use 'adb shell dumpsys package org.mozilla.firefox' to retrieve version informationAffected if A version number is returned that is lower than 103.0
-
Confirm version is in affected rangeCompare the retrieved version against the affected range: versions before 103.0. If the version shows 102.x or lower, or any pre-103 build, the device is affectedAffected if The installed version is less than 103.0 (for example 102.0, 102.1, 101.x, etc.)
A device is affected if Firefox for Android version 102.x or any version below 103.0 is installed and the session restore feature is enabled, as the long URL vulnerability would cause persistent UI hangs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped103.0
Update Firefox for Android to version 103 or later to patch this vulnerability. Organizations should ensure mobile devices have automatic updates enabled or push the update through their MDM solution.
Firefox 103.0 for Android
- Open Firefox for Android on your device
- Tap the three-dot menu and go to Settings
- Scroll down and tap on Firefox Firefox (or 'About Firefox')
- The app will check for updates - tap 'Update' if available
- Alternatively, open the Google Play Store, search for Firefox, and tap Update
- After updating, verify the version is 103.0 or higher in Settings > Firefox 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
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36317 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36317 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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