CVE-2004-0586
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 · uneditedacpRunner ActiveX 1.2.5.0 allows remote attackers to execute arbitrary code via the (1) DownLoadURL, (2) SaveFilePath, and (3) Download ActiveX methods.
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 confidenceThe acpRunner ActiveX control version 1.2.5.0 contains multiple insecure methods (DownLoadURL, SaveFilePath, Download) that allow remote attackers to download and execute arbitrary code on vulnerable systems. These methods likely lack proper validation of URL parameters and file path inputs, enabling arbitrary file writes and 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= 1.2.5.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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Locate the acpRunner ActiveX control component on the systemSearch for files named acpRunner.dll, acpRunner.ocx, or similar in the Windows system directories (System32, SysWOW64) and program directoriesAffected if The acpRunner ActiveX control DLL or OCX file is present on the system
-
Verify the installed version of the acpRunner componentRight-click the located DLL/OCX file, select Properties, and inspect the Version tab to obtain the exact file versionAffected if The reported file version is 1.2.5.0 exactly
-
Check if the ActiveX control is registered in the Windows registryOpen regedit and search under HKEY_CLASSES_ROOT for 'acpRunner' or the control's CLSID, then examine the Version or InprocServer32 entryAffected if The control is registered and the version key shows 1.2.5.0
-
Confirm the insecure methods are exposedUse a registry viewer to locate the Methods subkey under the control's CLSID in HKEY_CLASSES_ROOT\CLSID\{...}\Methods and verify DownLoadURL, SaveFilePath, or Download methods existAffected if Any of these three methods (DownLoadURL, SaveFilePath, Download) are listed as available methods
A system is affected if the acpRunner ActiveX control version 1.2.5.0 is installed and registered, exposing the DownLoadURL, SaveFilePath, or Download methods that can be invoked from web pages or malicious content.
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 dataUnregister the vulnerable acpRunner ActiveX control on affected systems, or implement Microsoft's kill bit to disable the control in Internet Explorer. Remove the control if no longer needed.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0586 — 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-2004-0586 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