FirefoxWeb browser · Mozilla

CVE-2019-11711

HIGH · 8.8 CVSS v3.1 Published 2019-07-23
Fix available
A fix is available. Upgrade to 60.8.0 / 68.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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
When an inner window is reused, it does not consider the use of document.domain for cross-origin protections. If pages on different subdomains ever cooperatively use document.domain, then either page can abuse this to inject script into arbitrary pages on the other subdomain, even those that did not use document.domain to relax their origin security. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.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 confidence

When an inner browser window is reused, the browser fails to properly consider document.domain settings that provide cross-origin protection between subdomains. This allows a page on one subdomain that has set document.domain to inject malicious script into arbitrary pages on another subdomain, even pages that did not use document.domain to relax their origin security, bypassing same-origin policy protections.

MitigationUpdate affected products to fixed versions (Firefox ESR 60.8+, Firefox 68+, Thunderbird 60.8+). Additionally, review and minimize use of document.domain in web applications as it weakens origin security boundaries.

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:< 60.8.0< 68.0
Debian LinuxOperating system
Affected:= 8.0
ThunderbirdApplication
Affected:< 60.8.0

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
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 checks

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

  1. Check Firefox version
    Run 'firefox --version' in terminal, or open Firefox and navigate to Help > About Firefox to view the version number
    Affected if Version is earlier than 60.8.0, or between 60.8.0 and 68.0 (non-ESR releases)
  2. Check Thunderbird version
    Run 'thunderbird --version' in terminal, or open Thunderbird and navigate to Help > About Thunderbird to view the version number
    Affected if Version is earlier than 60.8.0
  3. Identify document.domain usage in web applications
    Search source code repositories for 'document.domain' assignments using grep or similar tools: grep -r 'document.domain' /path/to/webapp
    Affected if Any web application hosted on subdomains sets document.domain to relax origin security boundaries
  4. Determine if affected browser hosts subdomain content
    Review whether the browser is used to access multiple subdomain sites where one subdomain could inject into another
    Affected if Browser accesses web applications across different subdomains where document.domain is in use

Environment is affected if running an affected Firefox or Thunderbird version AND serving or accessing web applications that utilize document.domain to relax same-origin policy between subdomains.

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.

From vendor data
Upgrade available Upgrade to 60.8.0 / 68.0 or later
Fixed in 60.8.068.0
Interim mitigation

Update affected products to fixed versions (Firefox ESR 60.8+, Firefox 68+, Thunderbird 60.8+). Additionally, review and minimize use of document.domain in web applications as it weakens origin security boundaries.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11711 — 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-2019-11711 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