CVE-2013-0762
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 the imgRequest::OnStopFrame function in Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.1, Thunderbird before 17.0.2, Thunderbird ESR 10.x before 10.0.12 and 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 unspecified 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 · high confidenceUse-after-free vulnerability in the imgRequest::OnStopFrame function in Mozilla products allows remote attackers to execute arbitrary code or cause heap memory corruption via unspecified vectors.
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 in the application menuAffected if The version is less than 10.0.12, or between 10.0.x and 17.0.1 inclusive, or less than 18.0 (specifically: < 10.0.12 OR >= 10.0 and < 10.0.12 OR >= 17.0 and < 17.0.2 OR < 18.0)
-
Check installed SeaMonkey versionRun 'seamonkey --version' or check via Help > About SeaMonkeyAffected if The version is less than 2.15
-
Check Firefox package version on RHEL/CentOS systemsRun 'rpm -q firefox' to query the installed Firefox packageAffected if The returned version is lower than the fixed versions (18.0, 10.0.12, or 17.0.2)
-
Check Firefox package version on Ubuntu/Debian systemsRun 'dpkg -l | grep firefox' or 'apt-cache policy firefox'Affected if The installed version is lower than the fixed versions for the respective Ubuntu release
-
Verify the vulnerability trigger conditionThe flaw is in imgRequest::OnStopFrame, triggered when processing image frames. Check if the browser handles animated images (GIF, WebP, or multi-frame images). No direct config check available - version check is definitive.Affected if Browser processes image content - the vulnerability can be triggered when loading malicious animated images in affected versions
You are affected if Firefox version is less than 10.0.12, between 10.0.x and 17.0.1, or less than 18.0; or SeaMonkey version is less than 2.15; or the browser package from affected RHEL/Ubuntu releases is installed without vendor patches.
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
Apply vendor patches by upgrading to Firefox 18.0 (or ESR 10.0.12/17.0.1), Thunderbird 17.0.2 (or ESR 10.0.12/17.0.1), or SeaMonkey 2.15 or later.
Firefox 18.0 (or ESR 10.0.12 / ESR 17.0.1); SeaMonkey 2.15
- 1. Close all instances of Firefox or SeaBrowser.
- 2. Back up bookmarks and any important browser data (optional but recommended).
- 3. Download the latest Firefox version (18.0 or later for stable release; 10.0.12 for ESR 10.x; 17.0.1 or later for ESR 17.x) from the official Mozilla website: https://www.mozilla.org/
- 4. For SeaMonkey users, download version 2.15 or later from the official SeaMonkey website.
- 5. Run the installer and follow the prompts to complete the installation.
- 6. Restart the browser after installation completes.
- 7. Verify the installed version by navigating to Help > About Firefox or About SeaMonkey.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0762 — 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-0762 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