CVE-2007-0942
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 SP4 on Windows 2000 SP4; 6 SP1 on Windows 2000 SP4; 6 and 7 on Windows XP SP2, or Windows Server 2003 SP1 or SP2; and possibly 7 on Windows Vista does not properly "instantiate certain COM objects as ActiveX controls," which allows remote attackers to execute arbitrary code via a crafted COM object from chtskdic.dll.
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 confidenceInternet Explorer fails to properly validate and instantiate certain COM objects as ActiveX controls. When a user visits a malicious webpage, the browser can be tricked into loading a crafted COM object from chtskdic.dll, allowing the attacker to execute arbitrary code with the user's privileges.
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.0.1= 6.0= 7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check your Internet Explorer versionOpen IE, click Help > About Internet Explorer, or run 'winver' command, or check registry key HKLM\Software\Microsoft\Internet Explorer\VersionAffected if The version is 5.0.1, 6.0, or 7.0
-
Verify if chtskdic.dll exists on the systemSearch for chtskdic.dll in system directories (C:\Windows\System32, C:\Windows\SysWOW64) using Windows Explorer search or command: dir /s C:\chtskdic.dllAffected if The file chtskdic.dll is present on the system and can be instantiated as an ActiveX control
-
Confirm if the vulnerable COM object is registeredCheck Windows registry under HKCR\CLSID for entries referencing chtskdic.dll or Bib神雕ActiveX Control, or use 'reg query' commands to search for related COM CLSIDsAffected if A COM object referencing chtskdic.dll is registered in the Windows registry
-
Check if ActiveX controls are enabledIn IE, go to Tools > Internet Options > Security > Custom Level, look for 'Run ActiveX controls and plugins' setting; also check 'ActiveX controls and plugins' options in the same sectionAffected if ActiveX controls and plugins are set to Enabled or Prompt for the relevant security zone (Internet/Restricted Sites)
-
Check if MS07-027 security update is installedRun 'reg query HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' looking for KB931768 (MS07-027), or use 'wmic qfe list' command, or check Windows Update historyAffected if The MS07-027 security update (KB931768) is NOT installed
Your environment is affected if you are running Internet Explorer 5.0.1 through 7.0, the chtskdic.dll file is present and its COM object is registered, ActiveX controls are enabled, and the MS07-027 patch is missing.
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.
dbcve · scopedApply the Microsoft security update MS07-027 (or subsequent cumulative updates that supersede it) to patch the vulnerable COM object instantiation behavior in Internet Explorer. Consider disabling the affected ActiveX control or upgrading to a newer browser version if patches are unavailable.
Microsoft Edge (Windows 10+) or Mozilla Firefox/Google Chrome (cross-platform)
- 1. Uninstall Internet Explorer 5.0.1, 6.0, or 7.0 from the affected Windows system
- 2. Upgrade to a supported browser: Microsoft Edge (for Windows 10/11) or Mozilla Firefox or Google Chrome for legacy systems
- 3. If Windows XP/Server 2003 must be used, apply Microsoft security update MS07-029 if available through Extended Support
- 4. Disable ActiveX controls in Internet Explorer settings as a workaround if upgrade is not immediately possible: Go to Tools > Internet Options > Security > Custom Level > Enable 'Initialize and script ActiveX controls not marked as safe' = Disable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0942 — 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-0942 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