cve.bz

CVE-2010-0555 microsoft

no score yetExploit referenceEPSS 21%

microsoft: no CVSS score yet. EPSS 21% estimated probability of exploitation activity in the next 30 days.

On this page
Microsoft Internet Explorer 5.01 SP4, 6, 6 SP1, 7, and 8 does not prevent rendering of non-HTML local files as HTML documents, which allows remote attackers to bypass intended access restrictions and read arbitrary files via vectors involving the product's use of text/html as the default content type for files that are encountered after a redirection, aka the URLMON sniffing vulnerability, a variant of CVE-2009-1140 and related to CVE-2008-1448.
EPSS
21% (unchanged from 21% a week ago; 21% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2010-0555 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2010-0555?via=ask-ai-copy and https://cve.bz/cve/CVE-2010-0555?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2010-0555 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
microsoft:internet_explorer6
microsoft:internet_explorer7
microsoft:windows_vistagold
microsoft:internet_explorer5.01:sp4
microsoft:internet_explorer6:sp1

References

Check your stackJSON