dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-0079

HIGH · 10.0 CVSS v2.0 Published 2011-05-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox 4.x before 4.0.1 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via vectors related to gfx/layers/d3d10/ReadbackManagerD3D10.cpp and unknown other vectors.

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

Memory corruption vulnerability in Mozilla Firefox 4.x browser engine's Direct3D10 rendering component (gfx/layers/d3d10/ReadbackManagerD3D10.cpp). Remote attackers can cause denial of service through application crashes or potentially achieve arbitrary code execution via unspecified attack vectors.

MitigationUpgrade Firefox to version 4.0.1 or later to patch the memory corruption vulnerabilities in the browser engine. Organizations should deploy the update enterprise-wide and verify installation.

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:= 4.0

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
Complete
Integrity
Complete
Availability
Complete

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

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. Confirm Firefox installation
    Check if Mozilla Firefox is installed on the system by looking for the executable at typical locations such as C:\Program Files\Mozilla Firefox\firefox.exe (Windows) or /Applications/Firefox.app (macOS) or in standard Linux package directories.
    Affected if Firefox is not installed on the system
  2. Identify installed Firefox version
    Launch Firefox and navigate to Help > About Firefox, or check the application version through the command line (e.g., firefox --version) or system registry on Windows.
    Affected if The installed version is exactly 4.0 (versions 4.0.1 and later are patched)
  3. Verify operating system is Windows with Direct3D10 support
    Confirm the system is running Windows Vista or later which includes Direct3D10 support, as the vulnerability exists in the Direct3D10 rendering component.
    Affected if The system is running Windows with Direct3D10 capabilities (DirectX 10 or higher)
  4. Confirm Direct3D10 rendering is in use
    Check if hardware acceleration and Direct3D10 rendering are enabled in Firefox by navigating to about:config and inspecting gfx.direct3d10.prefer-angle and related rendering preferences, or check Windows graphics driver status.
    Affected if Hardware acceleration using Direct3D10 is actively being used by the browser

A user is affected if they have Firefox version 4.0 installed on a Windows system with Direct3D10 rendering enabled.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch bugzilla.mozilla.org →
Interim mitigation

Upgrade Firefox to version 4.0.1 or later to patch the memory corruption vulnerabilities in the browser engine. Organizations should deploy the update enterprise-wide and verify installation.

Recommended fix High confidence

Firefox 4.0.1 or later (preferably latest stable Firefox release)

  1. Upgrade Mozilla Firefox from version 4.0 to version 4.0.1 or later to address the memory corruption vulnerabilities in the browser engine

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the patch applied

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-2011-0079 — 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-2011-0079 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