dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-42928

HIGH · 8.8 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.4 / 106.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Certain types of allocations were missing annotations that, if the Garbage Collector was in a specific state, could have lead to memory corruption and a potentially exploitable crash. This vulnerability affects Firefox < 106, Firefox ESR < 102.4, and Thunderbird < 102.4.

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 · moderate confidence

A missing Garbage Collector annotation in Firefox and Thunderbird allows memory corruption when the GC is in a specific state, potentially leading to exploitable crashes. The vulnerability stems from certain allocation types lacking proper GC safety annotations.

MitigationUpgrade to Firefox 106+, Firefox ESR 102.4+, or Thunderbird 102.4+ to patch the GC annotation vulnerability.

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:< 106.0
Firefox EsrWeb browser
Affected:< 102.4
ThunderbirdApplication
Affected:< 102.4

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
High

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

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

  1. Identify installed Mozilla product
    Check if Firefox (standard), Firefox ESR, or Thunderbird is installed. On Windows, look in Program Files. On macOS, check /Applications. On Linux, check package manager or /usr/lib.
    Affected if Any of these three products are installed
  2. Determine Firefox version
    Open Firefox, go to Help > About Firefox, or enter 'about:support' in the address bar. Note the full version number shown.
    Affected if Version is below 106.0 (for standard Firefox)
  3. Determine Firefox ESR version
    Open Firefox ESR, go to Help > About Firefox ESR, or enter 'about:support' in the address bar. Note the full version number shown.
    Affected if Version is below 102.4 (for Firefox ESR)
  4. Determine Thunderbird version
    Open Thunderbird, go to Help > About Thunderbird. Note the full version number shown.
    Affected if Version is below 102.4 (for Thunderbird)

User is affected if the installed version of Firefox is below 106.0, Firefox ESR is below 102.4, or Thunderbird is below 102.4, as these versions contain the missing GC annotation in the codebase.

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.4 / 106.0 or later
Fixed in 102.4106.0
Interim mitigation

Upgrade to Firefox 106+, Firefox ESR 102.4+, or Thunderbird 102.4+ to patch the GC annotation vulnerability.

Recommended fix High confidence

Firefox 106.0, Firefox ESR 102.4, or Thunderbird 102.4

  1. 1. Open Firefox, Firefox ESR, or Thunderbird
  2. 2. Navigate to the Help menu (or on macOS, Firefox/Thunderbird menu)
  3. 3. Select 'About Firefox' or 'About Thunderbird'
  4. 4. The application will automatically check for and download updates
  5. 5. If an update is available, click 'Update' or 'Restart to Update'
  6. 6. Alternatively, download the latest version from the official Mozilla website: https://www.mozilla.org/
  7. 7. For enterprise deployments, refer to Mozilla's enterprise documentation for managed deployment
Caveat Standard minor version upgrades typically do not introduce breaking changes; however, some legacy add-ons or extensions may not be compatible with newer versions

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
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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