dbcve.org
Dldrv2 Activex ControlApplication · Gigabyte

CVE-2010-1518

HIGH · 10.0 CVSS v2.0 Published 2010-08-02
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
Array index error in the SetDLInfo method in the GIGABYTE Dldrv2 ActiveX control 1.4.206.11 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via the item argument.

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

A critical array index error in the SetDLInfo method of the GIGABYTE Dldrv2 ActiveX control (v1.4.206.11) allows remote attackers to execute arbitrary code or cause memory corruption by providing a crafted value for the item argument.

MitigationDisable the GIGABYTE Dldrv2 ActiveX control in Internet Explorer and deploy compensating controls such as network segmentation or application whitelisting until a vendor patch is available.

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
Dldrv2 Activex ControlApplication
Affected:= 1.4.206.11

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

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

  1. Locate the GIGABYTE Dldrv2 ActiveX control on the system
    Search for the file Dldrv2.dll in typical ActiveX deployment locations such as C:\Windows\System32\ or C:\Program Files\Gigabyte\, or use the command 'reg query HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units' to find registered ActiveX controls
    Affected if The Dldrv2.dll file exists on the system indicating the ActiveX control is installed
  2. Verify the installed version of Dldrv2.dll
    Right-click the Dldrv2.dll file, select Properties, and check the File Version tab, or use the command 'wmic datafile where name="C:\\Windows\\System32\\Dldrv2.dll" get Version'
    Affected if The version is 1.4.206.11 exactly (the only affected version listed)
  3. Confirm the ActiveX control is registered in Windows
    Run 'reg query HKLM\SOFTWARE\Classes\CLSID' and search for CLSID values related to GIGABYTE Dldrv2, or check HKL\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved for the control's clsid
    Affected if The control has an active registry entry indicating it is registered and may be used by Internet Explorer
  4. Check if Internet Explorer allows the ActiveX control to run
    Open Internet Explorer, go to Internet Options > Security > Custom Level > ActiveX controls and plugins, or check the kill bit in registry at HKLM\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\ for the control's CLSID
    Affected if The control is not kill-bitged and is set to Allow or Prompt, meaning it can be instantiated by webpages
  5. Determine if the system has been used with browsers that could have loaded the vulnerable control
    Review browser history or proxy logs for access to Gigabyte-related download sites, or check for evidence of the Dldrv2 control being loaded in browser process memory using process inspection tools
    Affected if Evidence exists that the control was loaded or the system accessed sites that serve the vulnerable ActiveX component

A system is affected if the GIGABYTE Dldrv2 ActiveX control version 1.4.206.11 is installed and registered, and the control is not blocked from running in Internet Explorer.

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 the GIGABYTE Dldrv2 ActiveX control in Internet Explorer and deploy compensating controls such as network segmentation or application whitelisting until a vendor patch is available.

Fix this in Dldrv2 Activex Control Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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