CVE-2010-3747 in the critical feed json
An ActiveX control in RealNetworks RealPlayer 11.0 through 11.1, RealPlayer SP 1.0 through 1.1.4, and RealPlayer Enterprise 2.1.2 does not…
published 16y ago modified 4mo ago also EUVD-2010-3726
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 34.8%
- EPSS 34.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
An ActiveX control in RealNetworks RealPlayer 11.0 through 11.1, RealPlayer SP 1.0 through 1.1.4, and RealPlayer Enterprise 2.1.2 does not properly initialize an unspecified object component during parsing of a CDDA URI, which allows remote attackers to execute arbitrary code or cause a denial of service (uninitialized pointer dereference and application crash) via a long URI.
Is CVE-2010-3747 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
- Published
- First public exploit (Metasploit exploit/windows/browser/realplayer_cdda_uri)
Exploit prediction
34.79% 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/realplayer_cdda_uri RealNetworks RealPlayer CDDA URI Initialization Vulnerability metasploit exploit, normal rank, 2010-11-15
- EDB-16998 RealNetworks RealPlayer - CDDA URI Initialization (Metasploit) remote, 2011-03-17
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
-
service.real.com
/realplayer/security/10152010_player/en/
vendor-advisory
- zerodayinitiative.com /advisories/ZDI-10-210/
-
securityfocus.com
/bid/44144
vdb-entry
-
securityreason.com
/securityalert/8147
third-party-advisory
Sources
- CVE List CVE-2010-3747
- NVD CVE-2010-3747
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.