dbcve.org
RealplayerApplication · Realnetworks

CVE-2012-0922

HIGH · 9.3 CVSS v2.0 Published 2012-02-08
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
rvrender.dll in RealNetworks RealPlayer 11.x, 14.x, and 15.x before 15.02.71, and RealPlayer SP 1.0 through 1.1.5, allows remote attackers to execute arbitrary code via crafted flags in an RMFF file.

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

A vulnerability exists in rvrender.dll in RealNetworks RealPlayer (versions 11.x, 14.x, 15.x before 15.02.71, and RealPlayer SP 1.0-1.1.5) that allows remote code execution through crafted flags in malicious RMFF (RealMedia File Format) files. The DLL fails to properly validate input when parsing RMFF files, allowing an attacker to overflow buffers and inject arbitrary code.

MitigationUpdate RealPlayer to version 15.02.71 or later. Until patched, avoid opening RMFF files from untrusted sources and consider disabling RealPlayer file associations or temporarily uninstalling the software.

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:= 14.0.0= 14.0.1= 14.0.1.609= 14.0.1.633= 14.0.2= 14.0.3= 14.0.4= 14.0.5= 14.0.6= 14.0.7= 11.0= 11.0.1
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= 1.1.5

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. Confirm RealPlayer installation
    Check for RealPlayer installation directory (commonly C:\Program Files\Real\RealPlayer or C:\Program Files (x86)\Real\RealPlayer) and verify rvrender.dll exists in that folder
    Affected if RealPlayer is installed and rvrender.dll is present in the RealPlayer folder
  2. Identify installed RealPlayer version
    Open RealPlayer, go to Help > About RealPlayer, or right-click the RealPlayer executable and view Properties > Details to see the version number
    Affected if Version is 11.0, 11.0.1, any 14.x version before 15.0.2.71, or any RealPlayer SP version from 1.0.0 to 1.1.5
  3. Verify RMFF file association is active
    Check Windows file associations for .rm, .rmf, or .rmff extensions (RealMedia File Format). In Control Panel > Default Programs > Set Associations, verify these extensions are associated with RealPlayer
    Affected if RMFF file types (.rm, .rmf, .rmff) are associated with RealPlayer, allowing the application to automatically open these files

You are affected if RealPlayer version is 11.x, any 14.x version, or SP 1.0-1.1.5 AND rvrender.dll exists AND RMFF file associations are enabled, allowing malicious RMFF files to be processed by the vulnerable DLL.

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 version 15.02.71 or later. Until patched, avoid opening RMFF files from untrusted sources and consider disabling RealPlayer file associations or temporarily uninstalling the software.

Recommended fix High confidence

RealPlayer 15.0.2.71 or later

  1. Check current RealPlayer version by launching the application and navigating to Help > About RealPlayer
  2. Download RealPlayer 15.0.2.71 (or later version) from the official RealNetworks website at service.real.com
  3. Close all running instances of RealPlayer before installing
  4. Run the downloaded installer and follow the on-screen prompts to complete the upgrade
  5. Verify the installation was successful by checking Help > About RealPlayer shows version 15.0.2.71 or later
  6. Ensure antivirus software is current and scan the downloaded installer before execution
Caveat Upgrading RealPlayer may change file associations or reset user preferences; review settings after upgrade

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

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

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0922 — 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-2012-0922 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