CVE-2011-3664 json
Mozilla Firefox before 9.0, Thunderbird before 9.0, and SeaMonkey before 2.6 on Mac OS X do not properly handle certain DOM frame deletions…
published 2011-12-21 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3623
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
Mozilla Firefox before 9.0, Thunderbird before 9.0, and SeaMonkey before 2.6 on Mac OS X do not properly handle certain DOM frame deletions by plugins, which allows remote attackers to cause a denial of service (incorrect pointer dereference and application crash) or possibly have unspecified other impact via a crafted web site.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-3664 updated
Mozilla: Multiple security flaws fixed in v3.6.25 (Mac) and v9
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
References
-
mozilla.org
/security/announce/2011/mfsa2011-57.html
vendor-advisory
- bugzilla.mozilla.org /show_bug.cgi?id=649079
-
secunia.com
/advisories/47334
third-party-advisory
-
securitytracker.com
/id?1026447
vdb-entry
-
securitytracker.com
/id?1026446
vdb-entry
-
securitytracker.com
/id?1026445
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14574
vdb-entry, signature
-
secunia.com
/advisories/47302
third-party-advisory
Sources
- CVE List CVE-2011-3664
- NVD CVE-2011-3664
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.