CVE-2022-3266
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 · uneditedAn out-of-bounds read can occur when decoding H264 video. This results in a potentially exploitable crash. This vulnerability affects Firefox ESR < 102.3, Thunderbird < 102.3, and Firefox < 105.
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 confidenceAn out-of-bounds read vulnerability exists in the H264 video decoding path in Firefox, Firefox ESR, and Thunderbird. The vulnerability occurs during H264 video decoding and can lead to a potentially exploitable crash, allowing an attacker to read memory beyond allocated buffers.
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< 105.0< 102.3< 102.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Identify the installed Mozilla productOpen the application and go to Help > About (Firefox or Thunderbird) or type about:firefox in the address bar for Firefox. Note the product name and exact version number.Affected if The product is Mozilla Firefox, Firefox ESR, or Thunderbird with a version below 105.0 for Firefox or below 102.3 for ESR and Thunderbird.
-
Verify the exact version number against affected rangesCompare your installed version to these thresholds: Firefox < 105.0, Firefox ESR < 102.3, Thunderbird < 102.3. Check the Help > About dialog for the full version string (e.g., 102.2 or 104.0.1).Affected if The installed version falls below the thresholds: Firefox below 105.0, or Firefox ESR/Thunderbird below 102.3.
-
Confirm H264 video decoding capability is presentType about:support in the Firefox address bar and look for 'H264 hardware acceleration' or 'Video Decode' entries under Graphics. For Thunderbird, the same info appears in Help > Troubleshooting Information under Graphics.Affected if The application reports H264 decoding support (software or hardware) is available. The vulnerability exists in the H264 decoding path regardless of whether hardware acceleration is used.
-
Check if the application processes H264 contentReview your browser activity - if you have visited or received emails containing H264-encoded video content (common in MP4 files, web video, and many email attachments), the vulnerable decoding path was invoked.Affected if The application has processed or can process H264-encoded video content, which activates the vulnerable decoding code path.
You are affected if you are running Firefox below version 105.0, or Firefox ESR or Thunderbird below version 102.3, and the application has H264 video decoding capability enabled.
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.3105.0
Update affected products to Firefox ESR 102.3+, Thunderbird 102.3+, or Firefox 105+ to patch the vulnerability.
Firefox 105.0+ | Firefox ESR 102.3+ | Thunderbird 102.3+
- 1. Identify which Mozilla product is in use: Firefox (regular), Firefox ESR, or Thunderbird
- 2. Check the current version by clicking the menu button (three horizontal lines) > Help > About [Product Name]
- 3. For Firefox: Upgrade to version 105.0 or later
- 4. For Firefox ESR: Upgrade to version 102.3 or later
- 5. For Thunderbird: Upgrade to version 102.3 or later
- 6. Restart the application after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3266 — 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-3266 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