dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-40961

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 105.0 or later.
See remediation →
72/100
Remediation priority · Elevated
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
During startup, a graphics driver with an unexpected name could lead to a stack-buffer overflow causing a potentially exploitable crash.<br>*This issue only affects Firefox for Android. Other operating systems are not affected.*. This vulnerability affects 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 · high confidence

A stack-buffer overflow vulnerability exists in Firefox for Android's graphics driver loading code during startup. When a graphics driver with an unexpected (likely excessively long) name is encountered, the driver name is copied to a fixed-size stack buffer without proper bounds checking, leading to memory corruption and potential code execution. This is a classic input validation failure in the driver enumeration path on Android.

MitigationUpgrade Firefox for Android to version 105 or later. For custom Android applications with similar graphics driver handling, implement proper length validation and use safe string copy functions that respect buffer boundaries when processing driver names.

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:< 105.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Confirm product is Firefox for Android
    Verify the installed application is Mozilla Firefox for Android, not desktop Firefox. On Android, check the app package name (typically org.mozilla.firefox) in your device's app settings or package manager.
    Affected if The product is Firefox for Android rather than desktop Firefox or other Mozilla products.
  2. Check installed Firefox for Android version
    On Android, go to Settings > Apps > Mozilla Firefox > App info, or use a package manager command (e.g., 'adb shell dumpsys package org.mozilla.firefox | grep versionName') to retrieve the installed version number.
    Affected if The installed version is any version prior to 105.0 (e.g., 104.x, 103.x, etc.).
  3. Identify if graphics driver enumeration occurs at startup
    This vulnerability triggers during Firefox for Android startup when the application enumerates graphics drivers. The check is implicit: every startup triggers driver enumeration. No manual configuration needed to expose this code path.
    Affected if Firefox for Android starts and attempts to load graphics drivers, which occurs on every launch.
  4. Verify graphics driver handling is present
    Firefox for Android includes graphics driver loading code for WebGL and hardware acceleration. This is built into the application and cannot be disabled through user settings. The vulnerability exists in the driver name handling within this code path.
    Affected if The Firefox for Android build includes graphics driver support, which is standard for all builds.

A user is affected if they are running Firefox for Android version 104.x or earlier, since the stack-buffer overflow occurs in the graphics driver name handling during every startup.

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 105.0 or later
Fixed in 105.0
Interim mitigation

Upgrade Firefox for Android to version 105 or later. For custom Android applications with similar graphics driver handling, implement proper length validation and use safe string copy functions that respect buffer boundaries when processing driver names.

Recommended fix High confidence

Firefox 105.0 (for Android)

  1. Upgrade Firefox for Android to version 105.0 or later to address the stack-buffer overflow vulnerability in the graphics driver initialization.

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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