CVE-2007-6262 json
A certain ActiveX control in axvlc.dll in VideoLAN VLC 0.8.6 before 0.8.6d allows remote attackers to execute arbitrary code via crafted ar…
published 2007-12-06 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-6230
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.1%
- EPSS 11.1% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
A certain ActiveX control in axvlc.dll in VideoLAN VLC 0.8.6 before 0.8.6d allows remote attackers to execute arbitrary code via crafted arguments to the (1) addTarget, (2) getVariable, or (3) setVariable function, resulting from a "bad initialized pointer," aka a "recursive plugin release vulnerability."
Patch / fix
Timeline
- First public exploit (EDB-4688)
- Published
Exploit prediction
11.12% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-4688 VideoLAN VLC Media Player 0.86 < 0.86d - ActiveX Remote Bad Pointer Initialization dos, 2007-12-04
- securityfocus.com http://www.securityfocus.com/bid/26675 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
securityfocus.com
/bid/26675
vdb-entry, exploit, patch
-
secunia.com
/advisories/27878
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/38816
vdb-entry
- videolan.org /sa0703.html
-
vupen.com
/english/advisories/2007/4061
vdb-entry
- coresecurity.com /?action=item&id=2035
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14280
vdb-entry, signature
-
securityfocus.com
/archive/1/484563/100/0/threaded
mailing-list
-
securityreason.com
/securityalert/3420
third-party-advisory
Sources
- CVE List CVE-2007-6262
- NVD CVE-2007-6262
Fencer Vulns 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.