CVE-2008-4110 in the critical feed json
Buffer overflow in the SQLVDIRLib.SQLVDirControl ActiveX control in Tools\Binn\sqlvdir.dll in Microsoft SQL Server 2000 (aka SQL Server 8.0…
published 18y ago modified 4mo ago also EUVD-2008-4093
- cvss
- 7.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.4%
- EPSS 18.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Buffer overflow in the SQLVDIRLib.SQLVDirControl ActiveX control in Tools\Binn\sqlvdir.dll in Microsoft SQL Server 2000 (aka SQL Server 8.0) allows remote attackers to cause a denial of service (browser crash) or possibly execute arbitrary code via a long URL in the second argument to the Connect method. NOTE: this issue is not a vulnerability in many environments, since the control is not marked as safe for scripting and would not execute with default Internet Explorer settings.
Is CVE-2008-4110 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
18.42% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/31129 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.6 | AV:N/AC:H/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
-
securityfocus.com
/bid/31129
vdb-entry, exploit
-
securityfocus.com
/archive/1/496232/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/45186
vdb-entry
-
securityreason.com
/securityalert/4262
third-party-advisory
Sources
- CVE List CVE-2008-4110
- NVD CVE-2008-4110
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.