dbcve.org
FirefoxWeb browser · Mozilla

CVE-2019-11694

HIGH · 7.5 CVSS v3.0 Published 2019-07-23
Fix available
A fix is available. Upgrade to 60.7.0 / 67.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A vulnerability exists in the Windows sandbox where an uninitialized value in memory can be leaked to a renderer from a broker when making a call to access an otherwise unavailable file. This results in the potential leaking of information stored at that memory location. *Note: this issue only occurs on Windows. Other operating systems are unaffected.*. This vulnerability affects Thunderbird < 60.7, Firefox < 67, and Firefox ESR < 60.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

An information disclosure vulnerability in the Windows sandbox of Firefox and Thunderbird allows uninitialized memory values to leak from a broker to a renderer process when attempting to access an unavailable file. This occurs due to improper memory handling in the Windows-specific sandbox implementation, potentially exposing sensitive data stored in memory.

MitigationUpdate affected products to Firefox 67+, Thunderbird 60.7+, or Firefox ESR 60.7+ to patch the uninitialized memory leak in the Windows sandbox broker.

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.7.0< 67.0
ThunderbirdApplication
Affected:< 60.7.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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Identify installed Mozilla product
    Check if Firefox or Thunderbird is installed by looking for the application in the Windows Start Menu or checking Program Files directories
    Affected if Neither Firefox nor Thunderbird is installed (not affected)
  2. Determine product version on Windows
    Run 'firefox --version' or 'thunderbird --version' from command line, or open the application and go to Help > About to view the exact version number
    Affected if Version is Firefox < 60.7.0, Firefox < 67.0, or Thunderbird < 60.7.0 (affected)
  3. Confirm Windows platform
    Verify the operating system is Windows by checking system properties or running 'systeminfo | findstr /B /C:OS'
    Affected if Running on non-Windows OS (not affected, this is a Windows-specific sandbox flaw)
  4. Verify Windows sandbox is enabled
    Check Firefox/Thunderbird configuration: enter 'about:config' in address bar, search for 'security.sandbox.content.enabled' and confirm it is set to true (default on Windows)
    Affected if Sandbox is disabled (not vulnerable to this specific flaw)
  5. Confirm broker-to-renderer file access path
    This is an internal Windows sandbox mechanism; the vulnerability triggers when attempting to access an unavailable file through the sandbox broker - no direct user config check available
    Affected if Running vulnerable version on Windows with sandbox enabled (affected)

User is affected if running Firefox or Thunderbird on Windows with version below 60.7.0 (or below 67.0 for Firefox) and the Windows sandbox is enabled (default).

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.7.0 / 67.0 or later
Fixed in 60.7.067.0
Interim mitigation

Update affected products to Firefox 67+, Thunderbird 60.7+, or Firefox ESR 60.7+ to patch the uninitialized memory leak in the Windows sandbox broker.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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