cve.bz

CVE-2007-2223 microsoft xml core services: Year 2038 problem, Y2K38, Y2038, Epochalypse

no score yetExploitEPSS 49%Fix available

microsoft xml core services: no CVSS score yet. EPSS 49% estimated probability of exploitation activity in the next 30 days.

On this page
Microsoft XML Core Services (MSXML) 3.0 through 6.0 allows remote attackers to execute arbitrary code via the substringData method on a (1) TextNode or (2) XMLDOM object, which causes an integer overflow that leads to a buffer overflow.
EPSS
49% (unchanged from 49% a week ago; 49% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
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-2007-2223 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2007-2223?via=ask-ai-copy and https://cve.bz/cve/CVE-2007-2223?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-2007-2223 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:xml_core_services3.0
microsoft:xml_core_services4.0
microsoft:xml_core_services6.0
microsoft:xml_core_services5.0

Public exploits

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON