CVE-2023-23602
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 · uneditedA mishandled security check when creating a WebSocket in a WebWorker caused the Content Security Policy connect-src header to be ignored. This could lead to connections to restricted origins from inside WebWorkers. This vulnerability affects Firefox < 109, Firefox ESR < 102.7, and Thunderbird < 102.7.
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 confidenceA security check is mishandled when creating WebSockets inside WebWorkers, causing the Content Security Policy connect-src directive to be bypassed. This allows WebWorkers to establish connections to origins that should be restricted by CSP.
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< 109.0< 102.7< 102.7CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check Firefox versionOpen Firefox, go to Help > About Firefox (or navigate to about:support). Note the version number displayed.Affected if The version is below 109.0 (for standard Firefox) or below 102.7 (for Firefox ESR)
-
Check Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird. Note the version number displayed.Affected if The version is below 102.7
-
Verify WebWorker usage in web contentInspect web application code or use browser developer tools (Application tab > Service Workers/Web Workers) to determine if the application creates WebWorkers that initiate WebSocket connections.Affected if WebWorkers are used to establish WebSocket connections from web content
-
Check Content Security Policy configurationIn the affected browser, navigate to the target web application. Open Developer Tools (F12), go to the Console tab, and evaluate: console.log(document.securityPolicyViolations) or inspect response headers for 'Content-Security-Policy' header containing connect-src directive.Affected if The web application uses a CSP policy with connect-src restrictions and loads content in the affected browser version
You are affected if you run Firefox < 109.0 (or ESR < 102.7) or Thunderbird < 102.7 AND your web application uses WebWorkers that create WebSocket connections while enforcing a CSP connect-src policy.
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.7109.0
Upgrade affected endpoints to Firefox 109+, Firefox ESR 102.7+, or Thunderbird 102.7+ to apply the vendor patch.
Firefox 109.0, Firefox ESR 102.7, or Thunderbird 102.7 (depending on product)
- 1. Backup any critical data and configurations
- 2. Close all instances of Firefox, Firefox ESR, or Thunderbird
- 3. Download the latest version from the official Mozilla website (www.mozilla.org) or use your system's package manager
- 4. Install the update: For Firefox, upgrade to version 109.0 or later
- 5. For Firefox ESR users, upgrade to version 102.7 or later
- 6. For Thunderbird users, upgrade to version 102.7 or later
- 7. Verify the installed version matches or exceeds the fixed release (Help > About Firefox/Thunderbird)
- 8. Restart the application and verify WebSocket connections in WebWorkers respect CSP connect-src policies
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23602 — 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-23602 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