CVE-2011-4247
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 · uneditedRealNetworks RealPlayer before 15.0.0 allows remote attackers to execute arbitrary code via a crafted QCELP stream.
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 confidenceRealPlayer versions prior to 15.0.0 contain a vulnerability in the QCELP stream parsing functionality. A remote attacker can exploit this by tricking a user into opening a specially crafted media file containing malicious QCELP data, leading to arbitrary code execution with the privileges of the running user.
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<= 14.0.7= 4= 5= 6= 7= 8= 10.0= 10.5= 11.0= 11.0.1= 11.0.2= 11.0.2.1744CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify RealPlayer installationCheck for RealPlayer installation in typical locations such as C:\Program Files\Real\RealPlayer, or look for the executable (RealPlay.exe, RealPlayer.exe) on the system using file search or installed programs listAffected if RealPlayer is found installed on the system
-
Determine installed RealPlayer versionRight-click the RealPlayer executable, select Properties, and check the Details tab for version information, or open RealPlayer and look in the About/Help section for the version numberAffected if The version number is 14.0.7 or lower, or matches any of these: 4, 5, 6, 7, 8, 10.0, 10.5, 11.0, 11.0.1, 11.0.2, or 11.0.2.1744
-
Confirm QCELP codec supportOpen RealPlayer settings or preferences, navigate to the codecs or file types section, and check if QCELP playback support is enabled or registeredAffected if QCELP codec support is enabled or present in RealPlayer
-
Check for recent media file handlingReview the RealPlayer recent files list or examine the system for recently opened .qt, .mov, or other media files that may contain QCELP streamsAffected if RealPlayer has been used to open media files, particularly from untrusted sources
The system is affected if RealPlayer version is below 15.0.0 and the QCELP stream parsing functionality is present and enabled.
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 · scopedUpgrade RealPlayer to version 15.0.0 or later. Until patched, avoid opening media files from untrusted sources and consider blocking or filtering QCELP content at the network perimeter.
RealPlayer 15.0.0 or later
- Uninstall the existing RealPlayer version (versions 4, 5, 6, or any version up to 14.0.7)
- Download RealPlayer version 15.0.0 or later from the official Real.com website
- Install the downloaded version of RealPlayer
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-4247 — 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-4247 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