dbcve.org
Download ManagerApplication · Akamai Technologies

CVE-2007-1892

HIGH · 9.3 CVSS v2.0 Published 2007-04-18
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
Stack-based buffer overflow in Akamai Technologies Download Manager ActiveX Control (DownloadManagerV2.ocx) before 2.2.1.0 allows remote attackers to execute arbitrary code via unspecified vectors, a different issue than CVE-2007-1891.

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 confidence

Stack-based buffer overflow in Akamai Technologies Download Manager ActiveX Control (DownloadManagerV2.ocx) allows remote attackers to execute arbitrary code via unspecified vectors in versions prior to 2.2.1.0. This is a memory corruption vulnerability in client-side ActiveX software that enables code execution when exploited.

MitigationUpgrade Akamai Download Manager to version 2.2.1.0 or later, or disable/remove the vulnerable DownloadManagerV2.ocx ActiveX control from affected systems.

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
Download ManagerApplication
Affected:= 2.2.0.0

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 the DownloadManagerV2.ocx file on the system
    Search for DownloadManagerV2.ocx in typical Windows system directories such as C:\Windows\System32\ or C:\Windows\Downloaded Program Files\, or use the command 'dir /s C:\DownloadManagerV2.ocx' to find it across drives
    Affected if The file exists on the system, indicating the ActiveX control is installed
  2. Determine the file version of DownloadManagerV2.ocx
    Right-click the file, select Properties, then go to the Details tab to view the File Version, or use a command like 'wmic datafile where name="C:\Windows\System32\DownloadManagerV2.ocx" get Version'
    Affected if The version shown is 2.2.0.0 (the specifically listed affected version) or any version prior to 2.2.1.0
  3. Check if the ActiveX control is registered in the Windows registry
    Open Registry Editor and search for the CLSID associated with DownloadManagerV2.ocx, typically found under HKEY_CLASSES_ROOT\CLSID\ or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\
    Affected if The control is registered in the registry, meaning it is available for use by Internet Explorer or other applications
  4. Verify if the ActiveX control is marked safe for scripting in Internet Explorer
    Check the registry key HKEY_CLASSES_ROOT\CLSID\{CLSID}\Implemented Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4} or look for the 'SafeForScripting' value in the control's registry entry
    Affected if The control is registered as safe for scripting, meaning it can be invoked by malicious web pages

A system is affected if DownloadManagerV2.ocx is present with version 2.2.0.0 or any version prior to 2.2.1.0 and the ActiveX control is registered and enabled on the system.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Akamai Download Manager to version 2.2.1.0 or later, or disable/remove the vulnerable DownloadManagerV2.ocx ActiveX control from affected systems.

Recommended fix High confidence

Akamai Download Manager 2.2.1.0 or later

  1. Identify all systems with Akamai Download Manager version 2.2.0.0 installed
  2. Obtain Akamai Download Manager version 2.2.1.0 or later from the official vendor
  3. Uninstall the current version 2.2.0.0 from affected systems
  4. Install the updated version 2.2.1.0 or later
  5. Verify the installed version matches the patched release
  6. Test that the Download Manager functionality operates normally post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Download Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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