CVE-2023-4584
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 · uneditedMemory safety bugs present in Firefox 116, Firefox ESR 102.14, Firefox ESR 115.1, Thunderbird 102.14, and Thunderbird 115.1. 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 Firefox < 117, Firefox ESR < 102.15, Firefox ESR < 115.2, Thunderbird < 102.15, and Thunderbird < 115.2.
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 bugs in Firefox and Thunderbird allowed memory corruption that could potentially be exploited for arbitrary code execution. The vulnerability affects multiple product versions prior to the patched releases.
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< 117.0>= 115.0, < 115.2< 102.15< 115.2CVSS 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.
-
Identify installed Mozilla productCheck if Mozilla Firefox (standard or ESR) or Thunderbird is installed on the system. On Windows, look in Program Files or Program Files (x86). On macOS, check /Applications. On Linux, check /usr/lib/firefox or /usr/lib/thunderbird.Affected if Any of these three products are installed on the system
-
Check Firefox version on WindowsOpen Firefox, click Help > About Firefox. The version number is displayed in the dialog. Alternatively, run 'firefox --version' from command line on Linux, or check the executable properties on Windows.Affected if Version is 115.0 through 115.1.x (any version >= 115.0 but < 115.2, excluding 117.0+) or < 115.0 (for versions >= 115.0 but that's already covered)
-
Check Firefox ESR versionOpen Firefox ESR, click Help > About Firefox ESR. The version will show 'Firefox ESR' followed by a number (like 102.x). Run 'firefox-esr --version' on Linux.Affected if Version is below 102.15 (any 102.x version < 102.15)
-
Check Thunderbird versionOpen Thunderbird, click Help > About Thunderbird. The version number is displayed. Run 'thunderbird --version' on Linux.Affected if Version is below 115.2 (any version < 115.2)
-
Compare against affected version rangesMatch the installed version to the affected ranges: Firefox (standard) is affected if >= 115.0 and < 115.2, or < 115.0 but that's not in scope based on the provided ranges; Firefox ESR is affected if < 102.15; Thunderbird is affected if < 115.2.Affected if Installed version falls within any of these ranges: Firefox 115.0-115.1.x, Firefox ESR below 102.15, Thunderbird below 115.2
The environment is affected if any installed Firefox version is 115.0-115.1.x, any Firefox ESR version is below 102.15, or any Thunderbird version is below 115.2.
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.15115.2117.0
Update affected software to Firefox 117+, Firefox ESR 102.15+/115.2+, or Thunderbird 102.15+/115.2+ to remediate this vulnerability.
Firefox 117, Firefox ESR 102.15, Firefox ESR 115.2, Thunderbird 102.15, or Thunderbird 115.2 (depending on your release track)
- Check current Firefox or Thunderbird version by navigating to the application menu, selecting Help, then About (or by typing 'about:support' in the address bar)
- Close all instances of Firefox or Thunderbird
- Download the appropriate fixed version from the official Mozilla downloads page (www.mozilla.org): Firefox 117, Firefox ESR 102.15, Firefox ESR 115.2, Thunderbird 102.15, or Thunderbird 115.2 depending on your release track
- Run the downloaded installer and follow the prompts to complete the installation
- Restart the application and verify the version in About to confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4584 — 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-2023-4584 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