FirefoxWeb browser · Mozilla
CVE-2022-31746
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 · uneditedInternal URLs are protected by a secret UUID key, which could have been leaked to web page through the Referrer header. This vulnerability affects Firefox for iOS < 102.
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 iOS versions before 102 protected internal URLs using a secret UUID key, but this key could be leaked to external web pages through the Referrer header when users navigated to certain pages, potentially exposing protected internal URLs to attackers.
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
< 102.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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Firefox for iOS version installedOpen the Firefox for iOS app, go to Settings > Firefox for iOS (or tap the menu icon) > scroll down to the version number displayed under the app nameAffected if The displayed version number is less than 102.0 (for example, 101.x, 100.x, etc.)
-
Confirm the Referrer header policyIn Firefox for iOS, go to Settings > Privacy, then check the 'Send Referrer Header' or 'Referrer' setting. This controls whether the full URL is sent when navigating to external pagesAffected if The Referrer policy is set to send full URLs (not set to 'never' or 'default') and the Firefox version is below 102.0
-
Check for recent browser history involving internal URLsReview the browser history in Firefox for iOS for any visits to internal or restricted URLs that may contain the secret UUID pattern (typically looks like a long alphanumeric string in the URL path)Affected if The displayed version number is less than 102.0
A user is affected if Firefox for iOS version is below 102.0 and the Referrer header policy allows full URL transmission to external sites.
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 · scoped102.0
Update Firefox for iOS to version 102 or later, which contains the fix for this information disclosure vulnerability.
Firefox for iOS 102.0
- Open the App Store on your iOS device
- Locate Firefox for iOS in your installed applications or search for it
- Update Firefox for iOS to version 102.0 or later
- Alternatively, enable automatic app updates in iOS Settings > App Store to ensure timely security updates
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31746 — 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-31746 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