CVE-2007-0943
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 · uneditedUnspecified vulnerability in Internet Explorer 5.01 and 6 SP1 allows remote attackers to execute arbitrary code via crafted Cascading Style Sheets (CSS) strings that trigger memory corruption during parsing, related to use of out-of-bounds pointers.
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 confidenceVulnerability in Internet Explorer 5.01 and 6 SP1 where crafted Cascading Style Sheets (CSS) strings cause memory corruption through out-of-bounds pointer dereference during CSS parsing, potentially allowing remote arbitrary 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= 6.0= 5.01CVSS 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.
-
Check Internet Explorer version installedOpen Internet Explorer, then click Help > About Internet Explorer. Note the version number displayed (for example: Version 5.01 or Version 6.00.2800.1106). Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer for the Version value.Affected if The installed version is 5.01 or 6.0 (specifically build 6.0.2800.x with Service Pack 1)
-
Confirm Service Pack level on IE 6In IE 6, verify if Service Pack 1 is installed by checking the About dialog or reviewing the Windows Update history for 'Internet Explorer 6 Service Pack 1' installation date.Affected if Internet Explorer 6.0 with Service Pack 1 is installed (builds around 6.0.2800.1100-6.0.2800.1106)
-
Verify the vulnerable component is presentConfirm that the CSS parsing component (mshtml.dll) exists in the system. Check file version at C:\Windows\System32\mshtml.dll or C:\Program Files\Internet Explorer\mshtml.dll using right-click > Properties > Details.Affected if The mshtml.dll version corresponds to IE 5.01 or IE 6 SP1 (typically version 6.0.2800.x range)
-
Determine if IE is actively used as the default browserCheck Windows default browser settings in Settings > Default Apps > Web browser, or inspect the registry key HKEY_CLASSES_ROOT\http\shell\open\command to see which browser is associated with HTTP links.Affected if Internet Explorer is set as the default browser or commonly used for browsing
The system is affected if Internet Explorer version 5.01 or version 6.0 with Service Pack 1 is installed and actively used, as these versions contain the vulnerable CSS parsing code in mshtml.dll.
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 supported version of Internet Explorer or use an alternative modern web browser. For systems unable to upgrade, disable Active Scripting and restrict web browsing to trusted sites only.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0943 — 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-0943 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