FirefoxWeb browser · Mozilla

CVE-2023-23603

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-02
Fix available
A fix is available. Upgrade to 102.7 / 109.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Regular expressions used to filter out forbidden properties and values from style directives in calls to `console.log` weren't accounting for external URLs. Data could then be potentially exfiltrated from the browser. 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 confidence

A regex-based filter for style directives in console.log failed to properly sanitize external URLs, potentially allowing malicious websites to exfiltrate sensitive data from the browser through manipulated style attributes.

MitigationUpgrade Firefox to version 109 or later, Firefox ESR to 102.7 or later, or Thunderbird to 102.7 or later to apply the patched regex handling for URL-based style directives.

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:< 109.0
Firefox EsrWeb browser
Affected:< 102.7
ThunderbirdApplication
Affected:< 102.7

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Firefox version
    Navigate to Menu > Help > About Firefox, or enter 'about:support' in the address bar to view the version number under Application Basics
    Affected if Version is below 109.0 (regular Firefox)
  2. Check Firefox ESR version
    Navigate to Menu > Help > About Firefox, or enter 'about:support' in the address bar. ESR versions display 'ESR' in the version string
    Affected if Version is below 102.7 (Firefox ESR)
  3. Check Thunderbird version
    Navigate to Menu > Help > About Thunderbird, or enter 'about:support' in the address bar to view the version number
    Affected if Version is below 102.7 (Thunderbird)

A user is affected if they have Firefox below 109.0, Firefox ESR below 102.7, or Thunderbird below 102.7 installed and use the browser to view untrusted web content that could manipulate console.log style directives.

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 102.7 / 109.0 or later
Fixed in 102.7109.0
Interim mitigation

Upgrade Firefox to version 109 or later, Firefox ESR to 102.7 or later, or Thunderbird to 102.7 or later to apply the patched regex handling for URL-based style directives.

Recommended fix High confidence

Firefox 109.0, Firefox ESR 102.7, or Thunderbird 102.7

  1. 1. Check the current version of Firefox, Firefox ESR, or Thunderbird by navigating to the application's Help menu and selecting 'About'
  2. 2. For Firefox: Open the application, go to Menu > Help > About Firefox, and click 'Check for Updates' to automatically update to 109.0 or later
  3. 3. For Firefox ESR: Open the application, go to Menu > Help > About Firefox, and click 'Check for Updates' to automatically update to 102.7 or later
  4. 4. For Thunderbird: Open the application, go to Menu > Help > About Thunderbird, and click 'Check for Updates' to automatically update to 102.7 or later
  5. 5. Alternatively, download the latest version directly from the official Mozilla website (www.mozilla.org) and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,032.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23603 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23603 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