dbcve.org
IeApplication · Microsoft

CVE-2007-5344

MEDIUM · 6.8 CVSS v2.0 Published 2007-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Microsoft Internet Explorer 5.01 through 7 allows remote attackers to execute arbitrary code via a crafted website using Javascript that creates, modifies, deletes, and accesses document objects using the tags property, which triggers heap corruption, related to uninitialized or deleted objects, a different issue than CVE-2007-3902 and CVE-2007-3903, and a variant of "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

CVE-2007-5344 is a heap corruption vulnerability in Microsoft Internet Explorer versions 5.01 through 7. Attackers exploit this by crafting malicious web pages using JavaScript that manipulates document objects via the 'tags' property, triggering heap corruption through uninitialized or deleted objects and enabling arbitrary code execution.

MitigationUpgrade to a supported version of Internet Explorer (8 or higher) or migrate to modern browsers like Microsoft Edge, Chrome, or Firefox. Apply any available Microsoft security patches if running legacy systems in isolated environments.

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
IeApplication
Affected:= 5.x= 6.0
Internet ExplorerApplication
Affected:= 5= 5.01= 5.1= 5.2.3= 5.5= 6= 6.0= 6.0.2600= 6.0.2800= 6.0.2800.1106= 6.0.2900= 6.0.2900.2180

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
Partial
Integrity
Partial
Availability
Partial

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

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 installed Internet Explorer version
    Open Internet Explorer, click Help, then select About Internet Explorer. Alternatively, open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Version Vector to read the IE version.
    Affected if The displayed version falls within 5.0 through 7.0, specifically versions 5.x, 6.0, or any of the listed versions (5, 5.01, 5.1, 5.2.3, 5.5, 6, 6.0, 6.0.2600, 6.0.2800, 6.0.2800.1106, 6.0.2900, 6.0.2900.2180)
  2. Confirm JavaScript scripting is enabled
    In Internet Explorer, go to Tools > Internet Options > Security > Custom Level. Scroll to the 'Script ActiveX controls and binary behaviors' section and check if 'Script ActiveX controls' is enabled.
    Affected if JavaScript and ActiveX scripting are enabled in any security zone (particularly Internet or Intranet zones)
  3. Check for legacy IE usage on the system
    Open Command Prompt and run: reg query 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\IEXPLORE.EXE' to locate any installed IE executables, then verify their version.
    Affected if Internet Explorer versions 5.01 through 7 are installed on the system
  4. Verify if IE is set as the default browser
    Go to Control Panel > Default Programs > Set Default Programs. Check if Internet Explorer is selected as the default program for web browsing.
    Affected if Internet Explorer 5.x-7.x is the default browser and actively used for web browsing

Your environment is affected if Internet Explorer versions 5.01 through 7.x is installed and JavaScript/ActiveX scripting is enabled, as the vulnerability requires these conditions to be exploited through malicious web pages.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a supported version of Internet Explorer (8 or higher) or migrate to modern browsers like Microsoft Edge, Chrome, or Firefox. Apply any available Microsoft security patches if running legacy systems in isolated environments.

Fix this in Ie Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-5344 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