CVE-2011-2946
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 · uneditedUnspecified vulnerability in an ActiveX control in RealNetworks RealPlayer 11.0 through 11.1 and 14.0.0 through 14.0.5, RealPlayer SP 1.0 through 1.1.5, and RealPlayer Enterprise 2.0 through 2.1.5 allows remote attackers to execute arbitrary code via unknown vectors.
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 confidenceActiveX control vulnerability in RealNetworks RealPlayer versions 11.0-11.1, 14.0.0-14.0.5, SP 1.0-1.1.5, and Enterprise 2.0-2.1.5 allows remote attackers to execute arbitrary code via unspecified vectors.
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= 11.0= 11.1= 14.0.0= 14.0.1= 14.0.2= 14.0.3= 14.0.4= 14.0.5= 2.0= 2.1.2= 2.1.3= 2.1.4= 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= 1.1.5CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Find RealPlayer installation on the systemSearch for RealPlayer installation directories (typically C:\Program Files\Real\RealPlayer or C:\Program Files (x86)\Real\RealPlayer) or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\RealNetworks for installed componentsAffected if RealPlayer is found installed on the system
-
Identify the installed RealPlayer versionOpen RealPlayer and go to Help > About RealPlayer, or check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\RealNetworks\RealPlayer\Version for the version stringAffected if The installed version matches 11.0, 11.1, 14.0.0 through 14.0.5, SP versions 1.0.0 through 1.1.5, or Enterprise versions 2.0, 2.1.2, 2.1.3, 2.1.4
-
Confirm the product edition matches affected variantsVerify whether the installation is RealPlayer (standard), RealPlayer SP, or RealPlayer Enterprise by checking the registry or the About dialogAffected if The edition is one of the three affected variants (RealPlayer 11.x/14.x, RealPlayer SP 1.x, or RealPlayer Enterprise 2.x) with a version from the affected list
-
Verify ActiveX control usage is possibleCheck if Internet Explorer or other applications have ActiveX controls enabled (in IE: Internet Options > Security > Custom Level > ActiveX controls and plugins set to Enabled or Prompt)Affected if ActiveX controls can be loaded by browsers or other applications on the system
A user is affected if RealPlayer version 11.0-11.1, 14.0.0-14.0.5, SP 1.0-1.1.5, or Enterprise 2.0-2.1.4 is installed and ActiveX controls can be executed in the environment.
Generated from the published advisory. Verify against your own configuration.
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 · scopedDisable ActiveX controls in Internet Explorer and other affected applications, or upgrade to a patched RealPlayer version beyond 14.0.5.
Latest available RealPlayer version (14.0.5 or newer, or RealPlayer SP 1.1.5 if available)
- 1. Navigate to the official RealPlayer download page at service.real.com or search for the latest RealPlayer version
- 2. Download the most recent RealPlayer version (14.0.5 or later if available)
- 3. Uninstall the current RealPlayer installation via Windows Control Panel > Programs and Features
- 4. Install the latest RealPlayer version
- 5. Ensure Windows Update is current to patch any related ActiveX vulnerabilities
- 6. Consider migrating to an alternative media player if RealPlayer is no longer maintained for your platform
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2946 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-2946 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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