Skip to content
Fencer Intel
critical 10.0

CVE-2010-4742 in the critical feed json

Stack-based buffer overflow in a certain ActiveX control in MediaDBPlayback.DLL 2.2.0.5 in the Moxa ActiveX SDK allows remote attackers to…

published 15y ago modified 4mo ago also EUVD-2010-4707

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
56.4%
EPSS 56.4% chance of exploitation in 30 days, percentile 99%
public exploits
2
Metasploit and Exploit-DB

Summary

Stack-based buffer overflow in a certain ActiveX control in MediaDBPlayback.DLL 2.2.0.5 in the Moxa ActiveX SDK allows remote attackers to execute arbitrary code via a long PlayFileName property value.

Is CVE-2010-4742 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 Fencer

Timeline

  1. First public exploit (Metasploit exploit/windows/fileformat/moxa_mediadbplayback)
  2. Published

Exploit prediction

56.37% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/windows/fileformat/moxa_mediadbplayback MOXA MediaDBPlayback ActiveX Control Buffer Overflow metasploit exploit, average rank, 2010-10-19
  • EDB-16685 MOXA MediaDBPlayback - ActiveX Control Buffer Overflow (Metasploit) remote, 2010-11-05
  • metasploit.com http://www.metasploit.com/modules/exploit/windows/fileformat/moxa_mediadbplayback referenced PoC, tagged "exploit" by a source, unverified
  • reversemode.com http://reversemode.com/index.php?option=com_content&task=view&id=70&Itemid=1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

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.