How severe is CVE-2010-1518?

CVE-2010-1518 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2010-1518 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (88th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2010-1518?

CVE-2010-1518 affects Gigabyte Dldrv2 Activex Control. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2010-1518?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2010-1518 published?

CVE-2010-1518 was published on 2010-08-02 and last updated on 2026-06-16.

CVE-2010-1518

CVE-2010-1518 is a critical-severity vulnerability in Gigabyte Dldrv2 Activex Control with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-20.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 3% (88th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-20
Affected product: Gigabyte Dldrv2 Activex Control
Published: 2010-08-02
Last modified: 2026-06-16

Description

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.

Frequently asked questions

What is CVE-2010-1518?: 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.
How severe is CVE-2010-1518?: CVE-2010-1518 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2010-1518 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-1518?: CVE-2010-1518 affects Gigabyte Dldrv2 Activex Control. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2010-1518?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2010-1518 published?: CVE-2010-1518 was published on 2010-08-02 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:gigabyte:dldrv2_activex_control:1.4.206.11:*:*:*:*:*:*:*

More vulnerabilities in Gigabyte Dldrv2 Activex Control

CVE-2010-1517 — Critical (CVSS 10.0): The GIGABYTE Dldrv2 ActiveX control 1.4.206.11 allows remote attackers to (1) download arbitrary programs onto a client…

All CVEs affecting Gigabyte Dldrv2 Activex Control →

Other CWE-20 (Improper Input Validation) vulnerabilities

CVE-2026-93952 — Critical (CVSS 10.0): VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue may allow a remote attacker to access…
CVE-2026-77554 — Critical (CVSS 10.0): A malicious actor with access to the network could exploit an Improper Input Validation vulnerability found in UniFi…
CVE-2026-77537 — Critical (CVSS 10.0): A malicious actor with access to the network could exploit an Improper Input Validation vulnerability found in UniFi…
CVE-2026-48056 — Critical (CVSS 10.0): Streambert is a cross-platform Electron Desktop App to stream and download video content. Versions prior to 2.5.0…
CVE-2026-33267 — Critical (CVSS 10.0): Improper Input Validation vulnerability in Apache Traffic Server. This issue affects Apache Traffic Server: from 9.2.0…
CVE-2026-47668 — Critical (CVSS 10.0): DbGate is cross-platform database manager. In versions 7.1.8 and prior, DbGate's JSON script runner (`POST…

Browse all CWE-20 (Improper Input Validation) vulnerabilities →