CVE-2010-1681 in the critical feed json
Buffer overflow in VISIODWG.DLL before 10.0.6880.4 in Microsoft Office Visio allows user-assisted remote attackers to execute arbitrary cod…
published 16y ago modified 4mo ago also EUVD-2010-1701
- cvss
- 7.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 67.3%
- EPSS 67.3% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 3
- Metasploit and Exploit-DB
Summary
Buffer overflow in VISIODWG.DLL before 10.0.6880.4 in Microsoft Office Visio allows user-assisted remote attackers to execute arbitrary code via a crafted DXF file, a different vulnerability than CVE-2010-0254 and CVE-2010-0256.
Patch / fix
Is CVE-2010-1681 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/fileformat/visio_dxf_bof)
- Published
Exploit prediction
67.31% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/fileformat/visio_dxf_bof Microsoft Office Visio VISIODWG.DLL DXF File Handling Vulnerability metasploit exploit, good rank, 2010-05-04
- EDB-17451 Microsoft Visio - 'VISIODWG.dll .DXF' File Handling (MS10-028) (Metasploit) local, 2011-06-26
- EDB-14944 Microsoft Visio 2002 - '.DXF' Local Stack Overflow local, 2010-09-08
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
References
-
securityfocus.com
/bid/39836
vdb-entry, patch
-
exploit-db.com
/exploits/14944
exploit
-
securitytracker.com
/id?1023938
vdb-entry
-
securityfocus.com
/archive/1/511121/100/0/threaded
mailing-list
- coresecurity.com /content/ms-visio-dxf-buffer-overflow
Sources
- CVE List CVE-2010-1681
- NVD CVE-2010-1681
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.