FirefoxWeb browser · Mozilla
CVE-2022-34471
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 downloading an update for an addon, the downloaded addon update's version was not verified to match the version selected from the manifest. If the manifest had been tampered with on the server, an attacker could trick the browser into downgrading the addon to a prior version. 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 confidenceFirefox fails to verify that downloaded addon update versions match the version specified in the update manifest, allowing a man-in-the-middle or compromised update server to force downgrade of addons to vulnerable older versions by tampering with the manifest.
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.
-
Determine installed Firefox versionOpen Firefox, click the menu button (three horizontal lines), select Help, then About Firefox. Alternatively, run 'firefox --version' from command line or check the application file properties.Affected if The displayed version is any release prior to 102.0 (e.g., 101.x, 100.x, etc.)
-
Verify Firefox update configurationIn Firefox, go to Add-ons and Themes (Ctrl+Shift+A), click the gear icon next to 'Manage Your Extensions', and check 'Update Add-ons Automatically' setting.Affected if Automatic updates are enabled on a Firefox version below 102.0, as this allows the vulnerable update manifest verification to be exercised
-
Confirm presence of installed addons with update URLsIn Firefox Add-ons Manager (Ctrl+Shift+A), review installed extensions. Extensions with update URLs defined in their manifest are vulnerable to forced downgrade if the update server is compromised.Affected if Any addons with configured update URLs exist in Firefox versions below 102.0
A user is affected if Firefox version is below 102.0 AND they have addons with update capabilities configured, allowing a compromised update server to inject malicious older addon versions.
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 to version 102 or later where the version verification was fixed.
Firefox 102.0 or later
- Open Firefox and navigate to Help > About Firefox to check the current version
- If the version is below 102.0, download Firefox 102.0 or later from the official Mozilla website (www.mozilla.org)
- Install the Firefox update by running the downloaded installer
- Restart Firefox to complete the update
- Verify the update was successful by checking Help > About Firefox shows version 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
- Testing2.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-34471 — 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-34471 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