CVE-2011-0499 in the critical feed json
Buffer overflow in VideoSpirit Pro 1.6.8.1 and possibly earlier versions, and VideoSpirit Lite 1.4.0.1 and possibly other versions, allows…
published 2011-01-20 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0519
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 31.0%
- EPSS 31.0% chance of exploitation in 30 days, percentile 98%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
Buffer overflow in VideoSpirit Pro 1.6.8.1 and possibly earlier versions, and VideoSpirit Lite 1.4.0.1 and possibly other versions, allows user-assisted remote attackers to execute arbitrary code via a VideoSpirit project (.visprj) file containing a valitem element with a long "name" attribute. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
Timeline
- First public exploit (EDB-15936)
- Published
Exploit prediction
31.05% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/fileformat/videospirit_visprj VeryTools Video Spirit Pro metasploit exploit, good rank, 2011-04-11
- EDB-17153 VeryTools VideoSpirit Pro 1.70 - '.visprj' Local Buffer Overflow (Metasploit) local, 2011-04-11
- EDB-15936 VeryTools VideoSpirit Pro 1.68 - Local Buffer Overflow local, 2011-01-08
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/42876
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/42866
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64863
vdb-entry
Sources
- CVE List CVE-2011-0499
- NVD CVE-2011-0499
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.