FirefoxWeb browser · Mozilla
CVE-2023-25744
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 · uneditedMmemory safety bugs present in Firefox 109 and Firefox ESR 102.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 Firefox < 110 and Firefox ESR < 102.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 bugs in Firefox 109 and Firefox ESR 102.7 allowed memory corruption that could potentially be exploited to run arbitrary code via heap corruption. The bugs showed evidence of memory corruption exploitable with sufficient effort.
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
< 110.0
Firefox EsrWeb browser
< 102.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 installed Firefox versionOpen Firefox, then navigate to Help > About Firefox, or type 'about:support' in the address bar and press Enter. The version number is displayed at the top of the page.Affected if The displayed version is less than 110.0 (for example, 109 or earlier)
-
Determine if Firefox is ESR variantIn the about:support page, look for the 'Application' section or the version string. Firefox ESR versions typically include 'ESR' in the version name (for example, '102.7esr').Affected if The version string contains 'ESR' and the version is less than 102.8
-
Compare version against CVE thresholdsIf using regular Firefox, verify the version is 110.0 or later. If using Firefox ESR, verify the version is 102.8 or later.Affected if Regular Firefox is below 110.0 OR Firefox ESR is below 102.8
If the installed Firefox version is below 110.0 or the Firefox ESR version is below 102.8, the environment is affected by this CVE.
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.8110.0
Upgrade Firefox to version 110 or later, or Firefox ESR to version 102.8 or later, to remediate the memory corruption vulnerabilities.
Firefox 110.0 (standard) or Firefox ESR 102.8 (ESR)
- If using Firefox: Navigate to Menu > Help > About Firefox to check current version, or download Firefox 110.0 or later from the official Mozilla website
- If using Firefox ESR: Download Firefox ESR 102.8 or later from the Mozilla website or your organization's software distribution channel
- Close all running Firefox instances
- Install the updated Firefox version (110.0 for standard Firefox, 102.8 for ESR)
- Restart Firefox and verify the version under Menu > Help > About Firefox
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation3.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,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25744 — 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-25744 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