FirefoxWeb browser · Mozilla
CVE-2010-2755
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 · uneditedlayout/generic/nsObjectFrame.cpp in Mozilla Firefox 3.6.7 does not properly free memory in the parameter array of a plugin instance, which allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via a crafted HTML document, related to the DATA and SRC attributes of an OBJECT element. NOTE: this vulnerability exists because of an incorrect fix for CVE-2010-1214.
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 confidenceMemory management vulnerability in Firefox 3.6.7's nsObjectFrame.cpp fails to properly free memory in the parameter array of plugin instances when processing OBJECT elements with DATA and SRC attributes. This improper memory handling leads to memory corruption that can be exploited for denial of service or potentially arbitrary code execution. The flaw exists as a regression from an incomplete fix for CVE-2010-1214.
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
= 3.6.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox versionOpen Firefox and navigate to Help > About Mozilla Firefox, or enter 'about:support' in the address bar, or run 'firefox --version' from command lineAffected if The installed version is exactly 3.6.7 (no other version is affected)
-
Verify plugin support is enabledIn Firefox address bar, enter 'about:plugins' to list all available pluginsAffected if Any plugins are listed as enabled - the vulnerability affects memory handling in plugin instance parameters
You are affected only if running Firefox version 3.6.7 with plugins enabled; if your version differs or plugins are disabled, you are not vulnerable to this specific flaw.
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 · scopedOrganizations should update Firefox to a version with the corrected memory management code. Until patched, restrict or disable browser plugin execution, particularly avoid browsing untrusted sites with OBJECT elements.
Firefox 3.6.8 or later (or Firefox 4.0+/modern ESR release)
- Upgrade Mozilla Firefox from version 3.6.7 to version 3.6.8 or later to address the memory management error in nsObjectFrame.cpp
- If 3.6.x is required, upgrade to Firefox 3.6.8 which contains the corrected fix for this vulnerability
- Alternatively, upgrade to a newer stable release such as Firefox 4.0 or later for comprehensive security updates
- After upgrading, verify the installation by checking Help > About Firefox to confirm the version
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
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 locallyCheck whether your project pulls in CVE-2010-2755 — 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-2010-2755 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