FirefoxWeb browser · Mozilla
CVE-2019-11719
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 · uneditedWhen importing a curve25519 private key in PKCS#8format with leading 0x00 bytes, it is possible to trigger an out-of-bounds read in the Network Security Services (NSS) library. This could lead to information disclosure. 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 confidenceThe NSS library has an out-of-bounds read vulnerability when importing curve25519 private keys in PKCS#8 format that contain leading 0x00 bytes. This memory reading past buffer boundaries during key import leads to information disclosure, likely exposing adjacent memory contents.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check Mozilla Firefox versionOpen Firefox and navigate to Help > About Firefox, or type 'about:support' in the address bar. Locate the version number displayed.Affected if The version is below 60.8.0 or between 60.8.0 and 68.0 (non-inclusive).
-
Check Mozilla Thunderbird versionOpen Thunderbird and navigate to Help > About Thunderbird. Locate the version number displayed.Affected if The version is below 60.8.0.
-
Identify NSS library version (optional)On systems where the NSS library is accessible as a shared library, run 'pkgutil -info org.mozilla.nss' on macOS, or check the NSS version via 'nssutil -v' if available, or inspect the libnss3.so file properties on Linux.Affected if NSS version is earlier than the version bundled in Firefox 60.8.0/68.0 or Thunderbird 60.8.0.
-
Assess key import usageReview whether the application imports elliptic curve private keys, specifically curve25519 keys in PKCS#8 format. Check any logs or processes involving key import operations.Affected if The application imports curve25519 private keys in PKCS#8 format that contain leading 0x00 bytes.
You are affected if you run Firefox below 60.8.0 or below 68.0, or Thunderbird below 60.8.0, AND you import curve25519 private keys in PKCS#8 format containing leading 0x00 bytes.
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 NSS library to version containing the fix (included in Firefox ESR 60.8+, Firefox 68+, Thunderbird 60.8+) or update the affected products to patched versions.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11719 — 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-11719 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