FirefoxWeb browser · Mozilla

CVE-2006-2787

HIGH · 9.3 CVSS v2.0 Published 2006-06-02

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

EvalInSandbox in Mozilla Firefox and Thunderbird before 1.5.0.4 allows remote attackers to gain privileges via javascript that calls the valueOf method on objects that were created outside of the sandbox.

Technical summary

dbcve analysis · high confidence

EvalInSandbox in Mozilla Firefox and Thunderbird before 1.5.0.4 contains a sandbox escape vulnerability where JavaScript can call the valueOf method on objects created outside the sandbox, allowing remote attackers to gain elevated privileges and access objects outside the sandbox's security boundaries.

MitigationUpgrade affected installations of Mozilla Firefox or Thunderbird to version 1.5.0.4 or later to patch the sandbox escape vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FirefoxWeb browser

Affected:= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.5= 1.5.0.1= preview_release

ThunderbirdApplication

Affected:= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.5

CVSS breakdown

From the vector

Attack vector: Network
Complexity: M
Authentication: None
Confidentiality: Complete
Integrity: Complete
Availability: Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Firefox version

Run 'firefox --version' or check Help > About Mozilla Firefox to see the exact version number

Affected if Version is 1.0.x (any from 1.0 to 1.0.7), 1.5.x (any from 1.5 to 1.5.0.1), or labeled as preview_release
Identify installed Thunderbird version

Run 'thunderbird --version' or check Help > About Thunderbird to see the exact version number

Affected if Version is 1.0.x (any from 1.0 to 1.0.7) or 1.5.x (any from 1.5 to 1.5.0.1)
Determine if sandboxed JavaScript execution is in use

Check if the application processes untrusted JavaScript content, such as viewing HTML emails with JavaScript in Thunderbird, or loading remote content in Firefox with JavaScript enabled

Affected if The application processes or renders content that uses JavaScript in a sandboxed context (such as email messages, remote web pages, or HTML content from untrusted sources)

If either Firefox or Thunderbird is installed with a version between 1.0 and 1.5.0.1 (inclusive) and the application processes sandboxed JavaScript content, the environment is vulnerable to the sandbox escape.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade affected installations of Mozilla Firefox or Thunderbird to version 1.5.0.4 or later to patch the sandbox escape vulnerability.

Recommended fix High confidence

Firefox 2.0 or Thunderbird 2.0 (or later stable releases); the vulnerability was fixed in 1.5.0.4

1. Backup your profile data (bookmarks, passwords, emails) before upgrading
2. Download Firefox 2.0 or later from the official Mozilla website (mozilla.com/firefox)
3. Alternatively, download Thunderbird 2.0 or later from the official Mozilla website (mozilla.com/thunderbird)
4. Close all instances of Firefox or Thunderbird
5. Run the installer for the new version
6. During installation, choose to upgrade over existing installation to preserve settings
7. After installation, verify the version by clicking Help > About Firefox/Thunderbird

Caveat Minor: Some older extensions may be incompatible with Firefox 2.0+; re-check extension compatibility after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-2787 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2006-2787?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 2.8%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 9 hrs · Low

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2006-2787 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References