dbcve.org
ChromeWeb browser · Google

CVE-2014-1568

HIGH · 7.5 CVSS v2.0 Published 2014-09-25
Fix available
A fix is available. Upgrade to after 37.0.2062.120 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
Mozilla Network Security Services (NSS) before 3.16.2.1, 3.16.x before 3.16.5, and 3.17.x before 3.17.1, as used in Mozilla Firefox before 32.0.3, Mozilla Firefox ESR 24.x before 24.8.1 and 31.x before 31.1.1, Mozilla Thunderbird before 24.8.1 and 31.x before 31.1.2, Mozilla SeaMonkey before 2.29.1, Google Chrome before 37.0.2062.124 on Windows and OS X, and Google Chrome OS before 37.0.2062.120, does not properly parse ASN.1 values in X.509 certificates, which makes it easier for remote attackers to spoof RSA signatures via a crafted certificate, aka a "signature malleability" issue.

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

Mozilla NSS before 3.16.2.1/3.16.5/3.17.1 improperly parses ASN.1 values in X.509 certificates, enabling attackers to craft certificates with spoofed RSA signatures through signature malleability. This allows remote attackers to impersonate trusted entities by modifying signature values without invalidating the certificate chain.

MitigationUpdate affected Mozilla products (Firefox, Thunderbird, SeaMonkey) and Google Chrome to the specified patched versions or later, which contain the fixed NSS library. For embedded systems using NSS directly, update the NSS library to version 3.16.2.1, 3.16.5, or 3.17.1 or later.

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
ChromeWeb browser
Affected:<= 37.0.2062.120<= 37.0.2062.103= 37.0.2062.0= 37.0.2062.3= 37.0.2062.20= 37.0.2062.100= 37.0.2062.102
FirefoxWeb browser
Affected:<= 32.0= 31.0= 31.1.0= 32.0.1= 32.0.2
Firefox EsrWeb browser
Affected:= 24.8.0
Network Security ServicesApplication
Affected:<= 3.16.2.0= 3.2= 3.2.1= 3.3= 3.3.1= 3.3.2= 3.4= 3.4.1= 3.4.2= 3.5= 3.6= 3.6.1
SeamonkeyApplication
Affected:all versions<= 2.29= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9
ThunderbirdApplication
Affected:<= 24.8.0= 31.0= 31.1.0= 31.1.1

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 Mozilla Firefox version
    Open Firefox, click menu > Help > About Firefox, or visit about:support, to view the version number
    Affected if Version is 32.0, 32.0.1, 32.0.2, 31.0, 31.1.0, or <= 32.0 (all versions <= 32.0)
  2. Check Mozilla Firefox ESR version
    Open Firefox ESR, click menu > Help > About Firefox ESR, or visit about:support, to view the version number
    Affected if Version is 24.8.0
  3. Check Mozilla Thunderbird version
    Open Thunderbird, click menu > Help > About Thunderbird to view the version number
    Affected if Version is 24.8.0, 31.0, 31.1.0, or 31.1.1, or <= 24.8.0
  4. Check Mozilla SeaMonkey version
    Open SeaMonkey, click menu > Help > About SeaMonkey to view the version number
    Affected if Version matches any listed in the affected range (all versions and <= 2.29 are vulnerable)
  5. Check Google Chrome version
    Open Chrome, click menu > Help > About Google Chrome, or visit chrome://version, to view the version number
    Affected if Version is <= 37.0.2062.120, <= 37.0.2062.103, or matches 37.0.2062.0/3/20/100/102
  6. Check NSS library version directly
    For systems with NSS installed directly, run 'rpm -q nss' (RHEL/CentOS), 'dpkg -l libnss3' (Debian/Ubuntu), or inspect the NSS library file version using 'strings libnss3.so | grep -i "NSS"'
    Affected if NSS version is 3.16.2.0 or earlier, 3.2.x, 3.3.x, 3.4.x, 3.5, or 3.6.x

You are affected if any of your installed products (Firefox, Firefox ESR, Thunderbird, SeaMonkey, Chrome, or NSS library) match the vulnerable versions listed AND you rely on X.509 certificate chain validation, which is enabled by default in these products.

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 a release after 37.0.2062.120
Interim mitigation

Update affected Mozilla products (Firefox, Thunderbird, SeaMonkey) and Google Chrome to the specified patched versions or later, which contain the fixed NSS library. For embedded systems using NSS directly, update the NSS library to version 3.16.2.1, 3.16.5, or 3.17.1 or later.

Fix this in Chrome Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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