CVE-2010-1517
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 · uneditedThe GIGABYTE Dldrv2 ActiveX control 1.4.206.11 allows remote attackers to (1) download arbitrary programs onto a client system, and execute these programs, via vectors involving the dl method; and (2) download arbitrary programs onto a client system via vectors involving the SetDLInfo method in conjunction with the Bdl method.
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 confidenceThe GIGABYTE Dldrv2 ActiveX control version 1.4.206.11 contains insecure methods that allow remote attackers to download and execute arbitrary programs on vulnerable systems. Specifically, the dl method and the SetDLInfo/Bdl method combination can be leveraged to achieve remote code execution without user interaction beyond visiting a malicious webpage.
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.4.206.11CVSS 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 GIGABYTE Dldrv2 ActiveX control CLSID in the Windows registrySearch the Windows registry under HKEY_CLASSES_ROOT for entries containing 'Dldrv2' or search for the CLSID associated with this specific ActiveX controlAffected if The control CLSID is present in the registry, indicating the ActiveX control is installed
-
Verify the installed version of the Dldrv2 ActiveX controlCheck the version information in the registry for the control's CLSID entry or query the file version of the DLL if located in the systemAffected if The installed version equals exactly 1.4.206.11, matching the vulnerable version
-
Confirm the control is enabled for Internet ExplorerIn Internet Explorer, go to Tools > Internet Options > Security > Custom Level > ActiveX controls and plugins, or check the registry under 'Internet Settings\Zones\0' for the control's behavior settingsAffected if The control is allowed to run or download signed/unsigned ActiveX controls without prompts
-
Check if the kill bit is set for the control's CLSIDExamine the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\{CLSID} or HKEY_CLASSES_ROOT\CLSID\{CLSID} for the 'Enabled' DWORD value set to 0, or check for the kill bit in the registryAffected if The kill bit is NOT set (Enabled DWORD is not 0 or absent), meaning the control can still be instantiated and is vulnerable
A system is affected if the GIGABYTE Dldrv2 ActiveX control version 1.4.206.11 is installed and the kill bit has not been set for its CLSID in the registry.
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 vulnerable ActiveX control by setting the kill bit for its CLSID in the Windows registry, or remove the control entirely if no longer needed. Deploy the Microsoft Fix it solution or manually add the kill bit via registry modification to prevent instantiation in Internet Explorer.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1517 — 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-2010-1517 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