FirefoxWeb browser · Mozilla
CVE-2022-28289
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 · uneditedMozilla developers and community members Nika Layzell, Andrew McCreight, Gabriele Svelto, and the Mozilla Fuzzing Team reported memory safety bugs present in Thunderbird 91.7. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Thunderbird < 91.8, Firefox < 99, and Firefox ESR < 91.8.
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 confidenceMemory safety vulnerability in Thunderbird and Firefox caused by memory corruption bugs that could potentially allow arbitrary code execution. The bugs were present in versions prior to Thunderbird 91.8, Firefox 99, and Firefox ESR 91.8.
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
< 99.0
Firefox EsrWeb browser
< 91.8< 91.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Mozilla Firefox versionRun 'firefox --version' in terminal, or open Firefox, go to Help > About Firefox to view the version numberAffected if Version is present and less than 99.0 (for example, 98.x, 97.x, etc.)
-
Check Mozilla Firefox ESR versionRun 'firefox-esr --version' in terminal, or open Firefox ESR, go to Help > About Firefox to view the version numberAffected if Version is present and less than 91.8 (for example, 91.7.x, 91.6.x, etc.)
-
Check Mozilla Thunderbird versionRun 'thunderbird --version' in terminal, or open Thunderbird, go to Help > About Thunderbird to view the version numberAffected if Version is present and less than 91.8 (for example, 91.7.x, 91.6.x, etc.)
A system is affected if any installed Mozilla Firefox version is below 99.0, Firefox ESR is below 91.8, or Thunderbird is below 91.8.
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 · scoped91.899.0
Upgrade affected installations to Thunderbird 91.8, Firefox 99, Firefox ESR 91.8, or later versions to apply the vendor patch.
Firefox 99.0, Firefox ESR 91.8, or Thunderbird 91.8 (depending on product in use)
- 1. Determine the installed Firefox, Firefox ESR, or Thunderbird version by navigating to Help > About (or typing 'about:support' in the address bar)
- 2. If Firefox version is less than 99.0, upgrade to Firefox 99.0 or later
- 3. If Firefox ESR version is less than 91.8, upgrade to Firefox ESR 91.8 or later
- 4. If Thunderbird version is less than 91.8, upgrade to Thunderbird 91.8 or later
- 5. Restart the application after upgrade
- 6. Verify the fix by checking Help > About shows the patched version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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-28289 — 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-28289 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