dbcve.org
RealplayerApplication · Realnetworks

CVE-2010-3747

HIGH · 9.3 CVSS v2.0 Published 2010-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability exists in RealPlayer's ActiveX control where an unspecified object component is not properly initialized during CDDA URI parsing. A remote attacker can exploit this by providing a specially crafted long CDDA URI, triggering an uninitialized pointer dereference that leads to arbitrary code execution or application crash.

MitigationUpdate RealPlayer to a patched version if available, or disable the vulnerable ActiveX control via browser add-on settings or group policy. Avoid opening untrusted CDDA URIs or media files from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RealplayerApplication
Affected:= 11.0= 11.0.1= 11.0.2= 11.0.3= 11.0.4= 11.0.5= 11.1= 2.1.2
Realplayer SpApplication
Affected:= 1.0.0= 1.0.1= 1.0.2= 1.0.5= 1.1= 1.1.1= 1.1.2= 1.1.3= 1.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed RealPlayer version
    Open Windows Control Panel > Programs and Features, or run 'wmic product get name,version' to list installed software and locate RealPlayer
    Affected if The installed version matches one of these: RealPlayer 11.0-11.1, RealPlayer 2.1.2, or RealPlayer SP 1.0.0-1.1.4
  2. Verify ActiveX control presence
    Check for the RealPlayer ActiveX control registration in the Windows registry under HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units or look for 'rmoc3260.dll' in the RealPlayer installation directory
    Affected if The ActiveX control file (rmoc3260.dll or similar) is present and registered on the system
  3. Confirm CDDA protocol handler is registered
    Check Windows registry under HKCR\cdda\URL Protocol or HKLM\SOFTWARE\Classes\cdda to see if the CDDA URI scheme handler exists
    Affected if The CDDA protocol handler is registered, indicating the vulnerable parsing component is available to the ActiveX control

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update RealPlayer to a patched version if available, or disable the vulnerable ActiveX control via browser add-on settings or group policy. Avoid opening untrusted CDDA URIs or media files from unknown sources.

Recommended fix Moderate confidence

RealPlayer 12 or later (version after 11.1)

  1. 1. Uninstall the affected RealPlayer versions (11.0, 11.0.1, 11.0.2, 11.0.3, 11.1, SP 1.0.x, SP 1.1.x, or Enterprise 2.1.2)
  2. 2. Download and install a fixed version of RealPlayer from the official vendor (service.real.com)
  3. 3. Verify the installed version is not in the affected version list
  4. 4. Disable the affected ActiveX control in Internet Explorer as an additional mitigation: Go to Tools > Internet Options > Security > Custom Level, and disable 'Initialize and script ActiveX controls not marked as safe'
Caveat RealPlayer 12 changed the media library and streaming features; some legacy formats may not be supported

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Realplayer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-3747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-3747 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data