Skip to content
Fencer Intel
high 7.5

CVE-2011-3658 in the critical feed json

The SVG implementation in Mozilla Firefox 8.0, Thunderbird 8.0, and SeaMonkey 2.5 does not properly interact with DOMAttrModified event han…

published 2011-12-21 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3617

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
70.3%
EPSS 70.3% chance of exploitation in 30 days, percentile 99.3%
public exploits
2
Metasploit, Exploit-DB

Summary

The SVG implementation in Mozilla Firefox 8.0, Thunderbird 8.0, and SeaMonkey 2.5 does not properly interact with DOMAttrModified event handlers, which allows remote attackers to cause a denial of service (out-of-bounds memory access) or possibly have unspecified other impact via vectors involving removal of SVG elements.

Patch / fix

  • firefox-esr openSUSE Tumbleweed 128.5.1-1.1
  • MozillaFirefox openSUSE Tumbleweed 50.1.0-1.1
  • MozillaThunderbird openSUSE Tumbleweed 45.5.1-1.1

opensuse advisories openSUSE-SU-2024:14572-1openSUSE-SU-2024:10071-1openSUSE-SU-2024:10230-1

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-3658 updated

Mozilla: Multiple security flaws fixed in v3.6.25 (Mac) and v9

  • Red Hat All currently supported Red Hat products
    not 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

Timeline

  1. First public exploit (Metasploit exploit/windows/browser/mozilla_nssvgvalue)
  2. Published

Exploit prediction

70.34% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-399 Resource Management Errors

References

Sources

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.