CVE-2010-5193 in the critical feed json
Stack-based buffer overflow in the TIFMergeMultiFiles function in the SCRIBBLE.ScribbleCtrl.1 ActiveX control (ImageViewer2.ocx) in Viscom…
published 14y ago modified 4mo ago also EUVD-2010-5152
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 32.0%
- EPSS 32.0% chance of exploitation in 30 days, percentile 98%
- public exploits
- 3
- Metasploit and Exploit-DB
Summary
Stack-based buffer overflow in the TIFMergeMultiFiles function in the SCRIBBLE.ScribbleCtrl.1 ActiveX control (ImageViewer2.ocx) in Viscom Image Viewer CP Pro 8.0 and Gold 6.0 allows remote attackers to execute arbitrary code via a long strDelimit parameter.
Is CVE-2010-5193 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 FencerTimeline
- First public exploit (Metasploit exploit/windows/browser/imgeviewer_tifmergemultifiles)
- Published
Exploit prediction
31.97% 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/browser/imgeviewer_tifmergemultifiles Viscom Image Viewer CP Pro 8.0/Gold 6.0 ActiveX Control metasploit exploit, normal rank, 2010-03-03
- EDB-18123 Viscom Image Viewer CP Pro 8.0/Gold 6.0 - ActiveX Control (Metasploit) remote, 2011-11-17
- EDB-15668 Viscom Image Viewer CP Gold 6 - ActiveX 'TifMergeMultiFiles()' Remote Buffer Overflow remote, 2010-12-03
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
-
exploit-db.com
/exploits/15668
exploit
-
exploit-db.com
/exploits/18123
exploit
-
secunia.com
/advisories/42445
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/63666
vdb-entry
Sources
- CVE List CVE-2010-5193
- NVD CVE-2010-5193
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.