Skip to content
Fencer Intel
high 7.6

CVE-2010-0168 in the critical feed json

The nsDocument::MaybePreLoadImage function in content/base/src/nsDocument.cpp in the image-preloading implementation in Mozilla Firefox 3.6…

published 16y ago modified 4mo ago also EUVD-2010-0199

cvss
7.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.6%
EPSS 12.6% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

The nsDocument::MaybePreLoadImage function in content/base/src/nsDocument.cpp in the image-preloading implementation in Mozilla Firefox 3.6 before 3.6.2 does not apply scheme restrictions and policy restrictions to the image's URL, which might allow remote attackers to cause a denial of service (application crash or hang) or hijack the functionality of the browser's add-ons via a crafted SRC attribute of an IMG element, as demonstrated by remote command execution through an ssh: URL in a configuration that supports gnome-vfs with a nonstandard network.gnomevfs.supported-protocols setting.

Patch / fix

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

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

Is CVE-2010-0168 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-33798)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-33798 Mozilla Firefox 3.6 - Image Preloading Content-Policy Check Security Bypass remote, 2010-03-18

CVSS scores

assigned by version score vector
NVD 2.0 7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

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.