FirefoxWeb browser · Mozilla
CVE-2019-11729
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 · uneditedEmpty or malformed p256-ECDH public keys may trigger a segmentation fault due values being improperly sanitized before being copied into memory and used. 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 confidenceA memory safety vulnerability in the p256-ECDH key handling code causes a segmentation fault when empty or malformed public keys are processed. The values are copied into memory without proper sanitization, leading to invalid memory access. This is a denial-of-service vulnerability affecting cryptographic operations in affected products.
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
< 60.8.0< 68.0< 60.8.0CVSS 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
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mozilla Firefox versionOn Firefox, navigate to Help > About Firefox, or enter 'about:support' in the address bar and look for the 'Version' field. On Linux, run 'firefox --version'. On Windows, check the executable properties or use 'firefox -v' via command prompt.Affected if The displayed version is below 60.8.0 or is between 60.8.0 and 68.0 (not including 68.0)
-
Identify installed Mozilla Thunderbird versionOn Thunderbird, navigate to Help > About Thunderbird, or check the application properties. On Linux, run 'thunderbird --version'. On Windows, check the executable properties or use 'thunderbird -v' via command prompt.Affected if The displayed version is below 60.8.0
-
Determine if ECDH cryptography is in useThis vulnerability affects p256-ECDH key exchange operations. Check if the browser or mail client is configured to use ECDH cipher suites, or if you use extensions/plugins that perform ECDH key exchanges. The vulnerability triggers when processing malformed or empty public keys during ECDH handshakes.Affected if The application uses p256-ECDH key exchange and processes external public keys, combined with being in the affected version range
You are affected if you run Mozilla Firefox versions below 60.8.0 or below 68.0, or Thunderbird versions below 60.8.0, AND your application performs p256-ECDH cryptographic operations that could receive malformed public keys.
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.
From vendor data60.8.068.0
Upgrade to Firefox ESR 60.8+, Firefox 68+, or Thunderbird 60.8+ to receive the patched version with proper public key validation.
Fix this in Firefox
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11729 — 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-2019-11729 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