CVE-2008-3475

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-02. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 40%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Microsoft Internet Explorer 6 does not properly handle errors related to using the componentFromPoint method on xml objects that have been (1) incorrectly initialized or (2) deleted, which allows remote attackers to execute arbitrary code via a crafted HTML document, aka "Uninitialized Memory Corruption Vulnerability."

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
98.4%
KEV
Not listed

Published

October 15, 2008

Last Modified

April 23, 2026

Advisory Details (8)

Auto-updated May 2, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Microsoft Security Bulletin MS08-058 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2008/ms08-058
generic

ZDI-08-069 | Zero Day Initiative

http://www.zerodayinitiative.com/advisories/ZDI-08-069/
generic

VUPEN Security - Vulnerability Research and Intelligence

http://www.vupen.com/english/advisories/2008/2809
generic

'[security bulletin] HPSBST02379 SSRT080143 rev.1 - Storage Management Appliance (SMA), Microsoft Pat' - MARC

http://marc.info/?l=bugtraq&m=122479227205998&w=2
generic

Ivan Fratric's Security Blog: Internet Explorer 6 componentFromPoint() remote memory disclosure and remote code execution

http://ifsec.blogspot.com/2008/10/internet-explorer-6-componentfrompoint.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-04 06:27 UTCEPSS rescore
  2. 2026-07-02 14:00 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-28 14:03 UTCEPSS rescore
  7. 2026-06-28 04:52 UTCEPSS rescore
  8. 2026-06-27 03:04 UTCEPSS rescore
  9. 2026-06-25 13:46 UTCEPSS rescore
  10. 2026-06-25 13:46 UTCEPSS rescore
  11. 2026-06-24 14:02 UTCEPSS rescore
  12. 2026-06-24 14:02 UTCEPSS rescore
  13. 2026-06-23 21:29 UTCEPSS rescore
  14. 2026-06-23 21:29 UTCEPSS rescore
  15. 2026-06-22 14:22 UTCEPSS rescore
  16. 2026-06-22 14:22 UTCEPSS rescore
  17. 2026-06-21 14:53 UTCEPSS rescore
  18. 2026-06-21 14:53 UTCEPSS rescore
  19. 2026-06-21 01:56 UTCEPSS rescore
  20. 2026-06-21 01:56 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-17 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-16 17:49 UTCEPSS rescore
Show 41 more
  1. 2026-06-16 17:49 UTCEPSS rescore
  2. 2026-06-15 17:44 UTCEPSS rescore
  3. 2026-06-13 22:57 UTCEPSS rescore
  4. 2026-06-12 23:08 UTCEPSS rescore
  5. 2026-06-12 23:08 UTCEPSS rescore
  6. 2026-06-11 13:56 UTCEPSS rescore
  7. 2026-06-10 22:14 UTCEPSS rescore
  8. 2026-06-10 13:17 UTCEPSS rescore
  9. 2026-06-08 14:13 UTCEPSS rescore
  10. 2026-06-06 13:44 UTCEPSS rescore
  11. 2026-06-06 13:44 UTCEPSS rescore
  12. 2026-06-05 22:44 UTCEPSS rescore
  13. 2026-06-05 22:44 UTCEPSS rescore
  14. 2026-06-05 06:07 UTCEPSS rescore
  15. 2026-06-02 20:10 UTCEPSS rescore
  16. 2026-06-02 20:10 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-05-31 22:28 UTCEPSS rescore
  21. 2026-05-31 22:28 UTCEPSS rescore
  22. 2026-05-31 00:13 UTCEPSS rescore
  23. 2026-05-31 00:13 UTCEPSS rescore
  24. 2026-05-30 19:56 UTCEG score recompute
  25. 2026-05-30 19:56 UTCGHSA enrichment
  26. 2026-05-29 13:40 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-26 13:41 UTCEPSS rescore
  31. 2026-05-26 13:41 UTCEPSS rescore
  32. 2026-05-26 07:16 UTCEPSS rescore
  33. 2026-05-26 07:16 UTCEPSS rescore
  34. 2026-05-24 16:43 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-22 21:15 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 22:36 UTCEPSS rescore
  39. 2026-05-20 11:20 UTCEPSS rescore
  40. 2026-05-20 11:20 UTCEPSS rescore
  41. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2008-3475?
CVE-2008-3475 is a high vulnerability published on October 15, 2008. Microsoft Internet Explorer 6 does not properly handle errors related to using the componentFromPoint method on xml objects that have been (1) incorrectly initialized or (2) deleted, which allows remote attackers to execute arbitrary code via a crafted HTML document, aka "Uninitialized Memory…
When was CVE-2008-3475 disclosed?
CVE-2008-3475 was first published in the National Vulnerability Database on October 15, 2008, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2008-3475 actively exploited?
CVE-2008-3475 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2008-3475?
CVE-2008-3475 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2008-3475?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-3475, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2008-3475

Explore →

Is Your Infrastructure Affected by CVE-2008-3475?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.