dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-34469

HIGH · 8.1 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.0 or later.
See remediation →
88/100
Remediation priority · High
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 a TLS Certificate error occurs on a domain protected by the HSTS header, the browser should not allow the user to bypass the certificate error. On Firefox for Android, the user was presented with the option to bypass the error; this could only have been done by the user explicitly. <br>*This bug only affects Firefox for Android. Other operating systems are unaffected.*. 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

On Firefox for Android versions prior to 102, users could bypass TLS certificate errors on HSTS-protected domains, circumventing HSTS security protections against man-in-the-middle attacks. The browser incorrectly presented an option to proceed despite the certificate error on domains protected by the HSTS header, requiring explicit user action to bypass.

MitigationUpgrade Firefox for Android to version 102 or later to receive the security fix.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Firefox for Android is installed
    Open Android Settings, go to Apps, and look for Firefox in the app list. Alternatively, use ADB command: adb shell pm list packages | grep -i firefox
    Affected if Firefox for Android is not found on the device, so the vulnerability does not apply
  2. Identify the Firefox for Android version
    In Android Settings, go to Apps > Firefox > App info to view the version number. Alternatively, use ADB: adb shell dumpsys package org.mozilla.firefox | grep versionName
    Affected if The version displayed is below 102.0 (for example, 101.x, 100.x, etc.)
  3. Verify the vulnerable configuration is present
    This vulnerability is present by default in affected versions - no special configuration need be checked. The flaw is in how the browser handles certificate errors on HSTS-protected domains.
    Affected if The installed version is any version of Firefox for Android prior to 102.0

If Firefox for Android version 102.0 or higher is installed, the environment is not affected; otherwise, if the version is below 102.0, the user is affected by this vulnerability.

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 for Android to version 102 or later to receive the security fix.

Recommended fix High confidence

Firefox 102.0 (or later) for Android

  1. Open the Google Play Store app on the Android device
  2. Search for "Firefox" or "Mozilla Firefox"
  3. Tap on Firefox and select "Update" to install version 102.0 or later
  4. Alternatively, enable automatic updates in the Play Store to receive future security updates
  5. After updating, verify the version by opening Firefox > tapping the three-dot menu > Settings > About Firefox - the version should show 102.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.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-34469 — 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-34469 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