Internet ExplorerApplication · Microsoft

CVE-2007-0944

HIGH · 9.3 CVSS v2.0 Published 2007-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unspecified vulnerability in the CTableCol::OnPropertyChange method in Microsoft Internet Explorer 5.01 SP4 on Windows 2000 SP4; 6 SP1 on Windows 2000 SP4; and 6 on Windows XP SP2, or Windows Server 2003 SP1 or SP2 allows remote attackers to execute arbitrary code by calling deleteCell on a named table row in a named table column, then accessing the column, which causes Internet Explorer to access previously deleted objects, aka the "Uninitialized Memory Corruption Vulnerability."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Memory corruption vulnerability in Internet Explorer's CTableCol::OnPropertyChange method allows remote code execution when deleteCell is called on a named table row in a named table column, followed by accessing the column, causing use-after-free of deleted objects. Affects IE 5.01/6 on Windows 2000 SP4, XP SP2, and Server 2003 SP1/SP2.

MitigationAll affected systems (Windows 2000, XP SP2, Server 2003) are end-of-life with no vendor patches available; remediate by migrating to supported Windows versions and browsers, or isolate legacy systems on segmented networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Internet ExplorerApplication
Affected:= 5.01
IeApplication
Affected:= 6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Internet Explorer version
    Open Internet Explorer, click Help > About Internet Explorer, or run 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version' in Command Prompt
    Affected if Version reports 5.01 or 6.0 (exactly)
  2. Confirm Windows operating system version
    Run 'winver' or check System Properties, or run 'systeminfo' in Command Prompt
    Affected if Windows 2000 SP4, Windows XP SP2, or Windows Server 2003 SP1/SP2
  3. Verify the CTableCol component is present
    Check that iexplore.exe exists in the Program Files folder and that the browser renders HTML tables
    Affected if Internet Explorer is functional and capable of rendering HTML table elements
  4. Check for deleteCell usage in web content
    Review web application logs or code for use of JavaScript deleteCell method on table rows in named tables
    Affected if Web applications use named tables with deleteCell operations on table rows

If Internet Explorer 5.01 or 6.0 is installed on Windows 2000 SP4, XP SP2, or Server 2003 SP1/SP2, the system is affected by this vulnerability and cannot be patched.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

All affected systems (Windows 2000, XP SP2, Server 2003) are end-of-life with no vendor patches available; remediate by migrating to supported Windows versions and browsers, or isolate legacy systems on segmented networks.

Recommended fix Moderate confidence

Internet Explorer 7 or higher (or Microsoft Edge on supported Windows 10/11 systems)

  1. 1. Apply Microsoft security update MS07-027 (Cumulative Security Update for Internet Explorer) or later cumulative update that addresses this vulnerability.
  2. 2. Upgrade Internet Explorer to version 7 or higher (IE 7, 8, 9, 10, or 11) which are not affected by this vulnerability.
  3. 3. Alternatively, migrate to Microsoft Edge browser for modern Windows systems.
Caveat Upgrading from IE6 to IE7+ may cause compatibility issues with legacy web applications designed for older IE versions; test critical business applications before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Internet Explorer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,650
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0944 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data