CVE-2023-4583
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 · uneditedWhen checking if the Browsing Context had been discarded in `HttpBaseChannel`, if the load group was not available then it was assumed to have already been discarded which was not always the case for private channels after the private session had ended. This vulnerability affects Firefox < 117, Firefox ESR < 115.2, 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 · moderate confidenceIn Mozilla's HttpBaseChannel, when checking if a Browsing Context had been discarded, the code incorrectly assumed the context was already discarded if the load group was unavailable. This logic flaw affects private browsing channels after the private session ends, potentially leading to incorrect security state handling.
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.2< 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 productCheck which Mozilla application is installed: Firefox (standard), Firefox ESR, or Thunderbird. On Windows, look in Program Files; on macOS, check /Applications; on Linux, check /usr/lib or /opt.Affected if The product is Firefox, Firefox ESR, or Thunderbird.
-
Check Firefox versionIn Firefox, go to Help > About Firefox, or enter 'about:support' in the address bar. The version number is displayed at the top.Affected if Firefox version is below 117.0 (e.g., 116.x, 115.x, or earlier).
-
Check Firefox ESR versionIn Firefox ESR, go to Help > About Firefox, or enter 'about:support'. ESR versions typically include 'ESR' in the version string (e.g., 115.1esr).Affected if Firefox ESR version is below 115.2.
-
Check Thunderbird versionIn Thunderbird, go to Help > About Thunderbird, or enter 'about:support'. The version number is displayed at the top.Affected if Thunderbird version is below 115.2.
-
Verify if private browsing was usedThis vulnerability specifically affects private browsing channels after a private session ends. Check browser history or log recent private browsing sessions.Affected if Private browsing sessions were used and the browser was not updated after the session ended.
The environment is affected if Firefox is below 117.0, Firefox ESR is below 115.2, or Thunderbird is below 115.2, AND private browsing sessions were used in the affected version.
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 · scoped115.2117.0
Update Firefox to version 117 or later, Firefox ESR to 115.2 or later, and Thunderbird to 115.2 or later to receive the security patch.
Firefox 117.0, Firefox ESR 115.2, or Thunderbird 115.2
- Check the current version of Firefox, Firefox ESR, or Thunderbird installed (help > about)
- Download and install Firefox 117.0 or later, Firefox ESR 115.2 or later, or Thunderbird 115.2 or later from the official Mozilla website (www.mozilla.org)
- Restart the application after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4583 — 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-4583 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