LiveActive security incident?Get immediate response
CVE Record

CVE-2009-0419: Microsoft XML Core Services, as used in Microsoft Expression Web, Office, Internet Explorer 6 and 7, and ot...

Microsoft XML Core Services, as used in Microsoft Expression Web, Office, Internet Explorer 6 and 7, and other products, does not properly restrict access from web pages to Set-Cookie2 HTTP response headers, which allows remote attackers to obtain sensitive information from cookies via XMLHttpRequest calls, related to the HTTPOnly protection mechanism. NOTE: this issue reportedly exists because of an incomplete fix for CVE-2008-4033.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2009-0419 is an old Microsoft XML Core Services information-disclosure issue. A malicious web page could access Set-Cookie2 response headers through XMLHttpRequest, weakening HttpOnly cookie protection. Business risk depends on whether legacy Microsoft client software remains in use and whether sensitive session data is exposed through those cookies.

Executive priority

Treat this as a legacy exposure discovery item rather than an emergency unless affected software is still present. Priority should rise if old Microsoft browser or Office components process untrusted web content or handle sensitive authenticated sessions.

Technical view

The CVE describes improper restriction of web-page access to Set-Cookie2 HTTP response headers in Microsoft XML Core Services, used by Expression Web, Office, Internet Explorer 6 and 7, and other products. It is related to HttpOnly behavior and reportedly resulted from an incomplete fix for CVE-2008-4033.

Likely exposure

Exposure is most likely in legacy Windows desktop environments using affected Microsoft XML Core Services through Internet Explorer 6/7, Office, Expression Web, or dependent applications. The provided source bundle does not include exact affected versions, CPEs, patch levels, or modern support status.

Exploitation context

The source bundle does not identify active exploitation, and the CVE is not marked KEV. The described attack is remote and web-page based, but the bundle provides no confirmed exploit-in-the-wild evidence, no CVSS score, and no vendor remediation detail.

Researcher notes

Key gaps are affected version precision, patch availability, and severity scoring. The useful research path is asset correlation: identify MSXML consumers, confirm Set-Cookie2 handling, and compare installed patch levels against authoritative Microsoft guidance if available.

Mitigation direction

  • Inventory systems using legacy MSXML, Internet Explorer 6/7, Office, or Expression Web components.
  • Check Microsoft or vendor guidance for CVE-2009-0419 before selecting patches or workarounds.
  • Retire or isolate legacy client software where affected components are still required.
  • Avoid storing sensitive values in cookies exposed through Set-Cookie2 headers.
  • Prioritize compensating controls for users who must browse untrusted web content.

Validation and detection

  • Confirm whether any endpoints still run affected Microsoft XML Core Services-dependent products.
  • Review application responses for Set-Cookie2 usage carrying sensitive values.
  • Verify vendor patch or replacement status against CVE-2009-0419 and CVE-2008-4033.
  • Assess whether legacy browsers or Office web-content rendering paths remain enabled.
  • Document any systems where remediation is unavailable and compensating controls are used.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2009-0419 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.