dbcve.org
FirefoxWeb browser · Mozilla

CVE-2023-32209

HIGH · 7.5 CVSS v3.1 Published 2023-06-19
Fix available
A fix is available. Upgrade to 113.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A maliciously crafted favicon could have led to an out of memory crash. This vulnerability affects Firefox < 113.

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 vulnerability in Firefox's favicon handling allows a specially crafted malicious favicon to trigger an out-of-memory (OOM) crash, resulting in denial of service. The issue affects Firefox versions prior to 113 and is resolved by upgrading to Firefox 113 or later.

MitigationUpgrade Firefox to version 113 or later to patch the vulnerability. Organizations should ensure automated browser update mechanisms are enabled or deploy the update via patch management.

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:< 113.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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check if Firefox is installed
    Open a terminal or file explorer and look for the Firefox executable (firefox.exe on Windows, firefox on Linux/macOS) in common installation paths such as C:\Program Files\Mozilla Firefox\ or /Applications/Firefox.app/ on macOS, or /usr/lib/firefox/ on Linux. Alternatively, run 'where firefox' (Windows) or 'which firefox' (Linux/macOS) in a command prompt.
    Affected if Firefox is not found on the system, then this CVE is not applicable
  2. Retrieve Firefox version number
    Launch Firefox and navigate to the address bar, type 'about:support' and press Enter. On the displayed page, locate the 'Version' field in the 'Application Basics' section. Alternatively, click the menu button (three horizontal lines), select 'Help', then 'About Firefox' to display the version in a popup dialog.
    Affected if The version displayed is less than 113.0 (for example, 112.0, 112.0.1, 111.0, etc.)
  3. Confirm version consistency
    If you have direct access to the Firefox executable file, right-click the firefox.exe file (Windows), Get Info (macOS), or use 'rpm -q firefox' (Linux) or 'dpkg -l firefox' (Debian-based Linux) to cross-check that the reported version matches what you observed in the browser.
    Affected if The executable-based version also shows a number lower than 113.0, confirming the browser is vulnerable

A user is affected if Firefox is installed and the running version is any release prior to 113.0, regardless of which operating system is used.

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

Upgrade Firefox to version 113 or later to patch the vulnerability. Organizations should ensure automated browser update mechanisms are enabled or deploy the update via patch management.

Recommended fix High confidence

Firefox 113.0 or later

  1. Check the current Firefox version by navigating to menu > Help > About Firefox
  2. Download Firefox 113.0 or later from the official Mozilla website (www.mozilla.org)
  3. Close all Firefox instances
  4. Install the downloaded Firefox version
  5. Verify the upgrade by checking Help > About Firefox shows version 113.0 or later

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-2023-32209 — 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-2023-32209 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