dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-34474

MEDIUM · 6.1 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.0 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Even when an iframe was sandboxed with <code>allow-top-navigation-by-user-activation</code>, if it received a redirect header to an external protocol the browser would process the redirect and prompt the user as appropriate. This vulnerability affects Firefox < 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 confidence

A sandboxed iframe with the `allow-top-navigation-by-user-activation` attribute could be redirected via HTTP redirect headers to external protocols (like javascript: or data: URLs). This bypasses the user-activation requirement, allowing the browser to process the redirect and prompt the user without genuine user interaction.

MitigationUpgrade Firefox to version 102 or later. For web applications, implement Content Security Policy (CSP) to restrict iframe embedding and prevent external protocol handlers.

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:< 102.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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed Firefox version
    Open Firefox, go to Help > About Firefox, or run 'firefox --version' from command line, or check the version in the application properties on Windows
    Affected if The installed version is Mozilla Firefox prior to version 102.0
  2. Locate sandboxed iframes with top navigation permission
    Search web application source code (HTML files, templates, dynamic content) for iframe elements containing the 'sandbox' attribute with 'allow-top-navigation-by-user-activation'
    Affected if The web application serves content with iframes that have sandbox="allow-top-navigation-by-user-activation" and users access it via vulnerable Firefox versions
  3. Verify if HTTP redirects can target external protocols
    Review server-side redirect logic and any HTTP 3xx responses served to iframe contexts; check if the application allows redirects to javascript:, data:, or other dangerous URL schemes
    Affected if The application performs HTTP redirects that could be intercepted by sandboxed iframes to external protocols
  4. Confirm absence of mitigation headers
    Inspect HTTP response headers served with iframe content for Content-Security-Policy (CSP) frame-ancestors or sandbox directives; use browser devtools Network tab or curl -I to examine headers
    Affected if No CSP frame-ancestors or restrictive sandbox policy is defined, allowing untrusted iframe embedding

You are affected if running Mozilla Firefox versions prior to 102.0 AND your web application contains sandboxed iframes with allow-top-navigation-by-user-activation that could be redirected via HTTP headers to javascript: or data: URLs.

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

Upgrade Firefox to version 102 or later. For web applications, implement Content Security Policy (CSP) to restrict iframe embedding and prevent external protocol handlers.

Recommended fix High confidence

Firefox 102.0

  1. Upgrade Mozilla Firefox to version 102.0 or later

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
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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