CVE-2010-1932 in the critical feed json
Heap-based buffer overflow in XnView 1.97.4 and possibly earlier allows remote attackers to execute arbitrary code via a MultiBitMap (MBM)…
published 16y ago modified 4mo ago also EUVD-2010-1951
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.8%
- EPSS 10.8% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
Heap-based buffer overflow in XnView 1.97.4 and possibly earlier allows remote attackers to execute arbitrary code via a MultiBitMap (MBM) file with a Paint Data Section that contains a malformed Encoding field.
Is CVE-2010-1932 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 (EDB-34143)
- Published
Exploit prediction
10.76% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34143 XnView 1.97.4 - '.MBM' File Remote Heap Buffer Overflow remote, 2010-06-14
- coresecurity.com http://www.coresecurity.com/content/XnView-MBM-Processing-Heap-Overflow referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/40852 referenced PoC, tagged "exploit" by a source, unverified
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
-
coresecurity.com
/content/XnView-MBM-Processing-Heap-Overflow
exploit
-
securityfocus.com
/bid/40852
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/1468
vdb-entry, vendor-advisory
-
secunia.com
/advisories/40141
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59421
vdb-entry
-
securitytracker.com
/id?1024100
vdb-entry
Sources
- CVE List CVE-2010-1932
- NVD CVE-2010-1932
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.