CVE-2007-1683
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 · uneditedStack-based buffer overflow in the DoWebMenuAction function in the IncrediMail IMMenuShellExt ActiveX control (ImShExt.dll) allows remote attackers to execute arbitrary code via unspecified vectors.
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 confidenceStack-based buffer overflow in the DoWebMenuAction function of IncrediMail's IMMenuShellExt ActiveX control (ImShExt.dll) allows remote attackers to execute arbitrary code via malicious web content or crafted documents. This is a classic memory corruption vulnerability in a legacy email client ActiveX component.
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 dataall versionsCVSS 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 if IncrediMail is installedLook for IncrediMail in the list of installed programs via Control Panel > Programs and Features, or search for the IncrediMail installation directory (typically C:\Program Files\Incredimail or C:\Program Files (x86)\Incredimail)Affected if IncrediMail is present on the system
-
Locate the vulnerable ImShExt.dll fileSearch for ImShExt.dll in the IncrediMail installation folder, commonly found in paths like C:\Program Files\Incredimail\ImShExt.dll or C:\Program Files (x86)\Incredimail\ImShExt.dllAffected if ImShExt.dll exists on the system
-
Verify the ActiveX control is registeredCheck Windows Registry under HKLM\SOFTWARE\Microsoft\Code Store Database\SKUIDs\ or use regsvr32 to attempt registration of ImShExt.dll; check for CLSID entries related to IMMenuShellExt in HKCR\CLSIDAffected if The ActiveX control is registered in the Windows registry
-
Confirm browser ActiveX enablementCheck Internet Explorer settings (or Group Policy) for ActiveX controls: in IE, go to Internet Options > Security > Custom Level > ActiveX controls and scripts, or check registry under HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZonesAffected if ActiveX controls are allowed to run for the relevant zone (especially Internet or Intranet zones)
-
Identify exposed attack surfaceReview installed browsers and document handlers that may instantiate this ActiveX control, noting that IE and Office applications can load vulnerable ActiveX componentsAffected if Browsers or applications that support ActiveX are in use and the control can be invoked
If IncrediMail is installed with ImShExt.dll present and the ActiveX control is registered and enabled, the system is vulnerable to 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 dataDisable the IMMenuShellExt ActiveX control via browser kill bits or remove IncrediMail entirely. Deploy network-level filtering to block content targeting this legacy software.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1683 — 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-1683 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