dbcve.org
Mpeg4 Viewer Activex ControlApplication · Dlink

CVE-2009-1740

HIGH · 9.3 CVSS v2.0 Published 2009-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Multiple heap-based buffer overflows in the D-Link MPEG4 Viewer ActiveX Control (csviewer.ocx) 2.11.918.2006 allow remote attackers to execute arbitrary code via a long argument to the (1) SetFilePath and (2) SetClientCookie methods. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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 confidence

Heap-based buffer overflow in D-Link MPEG4 Viewer ActiveX Control (csviewer.ocx) version 2.11.918.2006 allows remote code execution via overly long strings passed to the SetFilePath and SetClientCookie methods. The vulnerability enables attackers to corrupt heap memory and execute arbitrary code through malicious web pages or HTML content.

MitigationDisable or implement a kill bit for the csviewer.ocx ActiveX control in Internet Explorer, or apply any vendor-supplied patch. Consider network-level filtering to block delivery vectors and enable DEP for browser processes as a defense-in-depth measure.

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
Mpeg4 Viewer Activex ControlApplication
Affected:= 2.11.918.2006

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

Work through these to decide whether this CVE applies to you.

  1. Locate csviewer.ocx on the system
    Search for csviewer.ocx in the Windows system directories, typically found in C:\Windows\System32\ or C:\Windows\SysWOW64\ (for 32-bit controls on 64-bit systems). Use the command: dir /s C:\csviewer.ocx or use Windows Search.
    Affected if The file csviewer.ocx exists on the system.
  2. Get the file version of csviewer.ocx
    Right-click on the located csviewer.ocx file, select Properties, then go to the Version tab. Alternatively, use PowerShell: (Get-Item 'C:\Windows\System32\csviewer.ocx').VersionInfo.FileVersion
    Affected if The reported file version is exactly 2.11.918.2006.
  3. Verify ActiveX control registration in Windows registry
    Check the registry for the control's CLSSID under HKEY_CLASSES_ROOT\CLSID. Look for entries containing 'MPEG4 Viewer' or 'csviewer' under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\ or HKEY_CLASSES_ROOT\csviewer.csviewer.1
    Affected if The control is registered as an ActiveX component in the Windows registry.
  4. Check if ActiveX control is enabled in Internet Explorer
    Open Internet Explorer, go to Tools > Manage Add-ons > Enable or Disable Add-ons. Look for 'D-Link MPEG4 Viewer' or 'csviewer' in the list of ActiveX controls.
    Affected if The D-Link MPEG4 Viewer ActiveX control is listed as Enabled.
  5. Confirm the vulnerable methods are available
    Use a script or tool to query the ActiveX control's available methods (e.g., OLE/COM Object Viewer or a PowerShell script using Get-Member on the COM object). Look for SetFilePath and SetClientCookie methods.
    Affected if The SetFilePath and SetClientCookie methods are exposed and accessible.

The system is affected if csviewer.ocx exists with version 2.11.918.2006 AND the ActiveX control is registered and enabled in Internet Explorer, allowing the vulnerable SetFilePath or SetClientCookie methods to be invoked from malicious web content.

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

Disable or implement a kill bit for the csviewer.ocx ActiveX control in Internet Explorer, or apply any vendor-supplied patch. Consider network-level filtering to block delivery vectors and enable DEP for browser processes as a defense-in-depth measure.

Fix this in Mpeg4 Viewer Activex Control Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-1740 — 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-2009-1740 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