CVE-2007-5347
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 · uneditedMicrosoft Internet Explorer 5.01 through 7 allows remote attackers to execute arbitrary code via "unexpected method calls to HTML objects," aka "DHTML Object 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 · moderate confidenceMemory corruption vulnerability in Microsoft Internet Explorer 5.01 through 7 allows remote attackers to execute arbitrary code via unexpected method calls to HTML objects (DHTML objects). The vulnerability stems from improper handling of method calls to HTML objects, leading to memory corruption that can be exploited for code execution.
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= 5.x= 6.0= 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.2180CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Internet Explorer versionOpen Internet Explorer, click Help, then select About Internet Explorer. Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version' from command prompt.Affected if The displayed version matches any of these: 5.x, 5.01, 5.1, 5.2.3, 5.5, 6.x, 6.0.2600, 6.0.2800, 6.0.2800.1106, 6.0.2900, 6.0.2900.2180, or any version from 5 through 7 that is not patched.
-
Confirm full version numberIn the About dialog, note the full version string (e.g., 6.0.2900.2180). For registry method, check the 'Version' and 'svcVersion' values under HKLM\SOFTWARE\Microsoft\Internet Explorer.Affected if The version is exactly one of those listed in the affected versions, or falls between 5.0 and 7.0 without security updates.
-
Check Windows version contextRun 'winver' or check system properties to identify the Windows version, then cross-reference with known IE bundle versions.Affected if Running an older Windows version that shipped with a vulnerable IE version (IE 5.01 through IE 7).
If Internet Explorer version is 5.x, 5.01, 5.1, 5.2.3, 5.5, 6.x, or 7.x without the MS07-069 security update, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a newer version of Internet Explorer or switch to an alternative browser. Implement network-level protections such as web proxies with malware detection. Disable ActiveScripting in IE as a defense-in-depth measure.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5347 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-5347 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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