dbcve.org
FirefoxWeb browser · Mozilla

CVE-2007-5967

MEDIUM · 6.5 CVSS v3.1 Published 2021-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
A flaw in Mozilla's embedded certificate code might allow web sites to install root certificates on devices without user approval.

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 · moderate confidence

A flaw in Mozilla's embedded certificate code allowed malicious or compromised websites to silently install root certificates on user devices without any user interaction or approval. This could enable attackers to establish fraudulent certificate chains and perform man-in-the-middle attacks.

MitigationDeploy the vendor patch for the affected Mozilla browser version. Consider implementing browser hardening policies or enterprise certificate management to control root certificate installation, and educate users about the risks of trusting unknown websites.

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:all versions

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Firefox installation
    Check if Mozilla Firefox is installed by looking for the executable in common locations (C:\Program Files\Mozilla Firefox on Windows, /Applications/Firefox.app on Mac, or via package manager on Linux). Also check Start menu or application listings.
    Affected if Firefox is present on the system regardless of version
  2. Check installed Firefox version
    Run 'firefox --version' from command line, or open Firefox and go to Help > About Firefox to display the exact version number.
    Affected if Any version of Firefox is installed (all versions are affected)
  3. Review installed root certificates
    Access Firefox certificate manager: open Firefox, go to Options/Preferences > Privacy & Security > Scroll to Certificates > Click 'View Certificates'. Examine the 'Authorities' tab for any unfamiliar or suspicious root certificate authorities.
    Affected if Any root certificate exists that was not intentionally installed by the user or enterprise administrator
  4. Check for recently added certificates
    In the Firefox Certificate Manager, sort the 'Authorities' tab by 'Serial Number' or check certificate validity dates to identify certificates added around the time of potential exploitation (2007 or later).
    Affected if Certificates with validity periods starting after 2007 are present and were not intentionally added
  5. Inspect browser certificate policy settings
    Enter 'about:config' in Firefox address bar, search for 'security.enterprise_roots.enabled' and 'security.default_personal_cert' to check certificate management configuration.
    Affected if Policy settings allow automatic root certificate installation without user prompt

A user is affected if they have any version of Firefox installed and possess root certificates in the browser that were added without deliberate user action, as the vulnerability allowed silent unauthorized certificate installation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Deploy the vendor patch for the affected Mozilla browser version. Consider implementing browser hardening policies or enterprise certificate management to control root certificate installation, and educate users about the risks of trusting unknown websites.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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