CVE-2013-0763
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 · uneditedUse-after-free vulnerability in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.1, Thunderbird before 17.0.2, Thunderbird ESR 17.x before 17.0.1, and SeaMonkey before 2.15 allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) via vectors related to Mesa drivers and a resized WebGL canvas.
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 confidenceA use-after-free vulnerability in Mozilla products allows remote attackers to execute arbitrary code through corrupted heap memory. The flaw exists in the WebGL implementation when interacting with Mesa drivers during canvas resizing operations, causing freed memory to be accessed after deallocation.
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< 18.0>= 10.0, < 10.0.12>= 17.0, < 17.0.2= 5.0= 6.0= 5.9= 6.3= 5.0= 6.0= 5.9= 5.0= 6.0= 10.04= 11.10= 12.04= 12.10< 2.15CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Firefox versionRun 'firefox --version' or go to Help > About Firefox to view the exact version numberAffected if Version is < 10.0.12, or >= 10.0 and < 17.0.2, or >= 17.0 and < 17.0.2, or < 18.0 (specifically < 18.0)
-
Check installed SeaMonkey versionRun 'seamonkey --version' or check the application propertiesAffected if Version is < 2.15
-
Verify WebGL is enabled in the browserIn Firefox, type 'about:config' in the address bar, search for 'webgl.enabled-for-all-sites' and check if it is set to trueAffected if WebGL is enabled and the browser version falls within the affected ranges
-
Check Red Hat Enterprise Linux version (if applicable)Run 'cat /etc/redhat-release' to identify the RHEL versionAffected if Running RHEL Desktop 5.0, 6.0; RHEL Server 5.0, 6.0; RHEL Workstation 5.0, 6.0; RHEL EUS 5.9, 6.3; or RHEL Server Aus 5.9 with vulnerable Mozilla products installed
-
Check Ubuntu Linux version (if applicable)Run 'cat /etc/lsb-release' to identify the Ubuntu versionAffected if Running Ubuntu 10.04, 11.10, 12.04, or 12.10 with vulnerable Mozilla products installed
You are affected if you are running any Firefox version < 18.0 (specifically 10.0.x before 10.0.12, or 17.x before 17.0.2), SeaMonkey version < 2.15, or any Mozilla product on the listed RHEL/Ubuntu versions, AND WebGL is enabled in the browser.
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.
dbcve · scoped2.1510.0.1217.0.2
Upgrade affected Mozilla products (Firefox, Firefox ESR, Thunderbird, Thunderbird ESR, SeaMonkey) to the patched versions specified in the advisory (18.0+, 17.0.1+, 17.0.2+) to remediate the vulnerability.
Firefox 18.0 or later (or Firefox ESR 17.0.1+); SeaMonkey 2.15 or later; Ubuntu 12.10 to later stable Ubuntu release
- 1. Identify the installed Mozilla product (Firefox, SeaMonkey, or Thunderbird) and current version using: 'firefox --version', 'seamonkey --version', or 'thunderbird --version'
- 2. For Firefox users: Upgrade to Firefox 18.0 or later. Download from https://www.mozilla.org/firefox/ or use system package manager
- 3. For Firefox ESR users: Upgrade to Firefox ESR 17.0.1 or later
- 4. For SeaMonkey users: Upgrade to SeaMonkey 2.15 or later. Download from https://www.seamonkey-project.org/
- 5. For Thunderbird users: Upgrade to Thunderbird 17.0.2 or later (if applicable)
- 6. After upgrade, verify the new version is installed by running the version command again
- 7. Restart the browser application completely to ensure the patched version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2013-0763 — 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-2013-0763 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