dbcve.org
RealplayerApplication · Realnetworks

CVE-2012-0926

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
The RV10 codec in RealNetworks RealPlayer 11.x, 14.x, and 15.x before 15.02.71, and RealPlayer SP 1.0 through 1.1.5, does not properly handle height and width values, which allows remote attackers to execute arbitrary code via a crafted RV10 RealVideo video 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 confidence

The RV10 RealVideo codec in RealPlayer fails to validate height and width values from crafted video streams, allowing a heap/stack buffer overflow that enables remote code execution.

MitigationUpdate to RealPlayer 15.02.71 or later; until patched, restrict or disable RealPlayer and warn users against opening untrusted RealVideo content.

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 directories such as C:\Program Files\Real\RealPlayer or C:\Program Files (x86)\Real\RealPlayer. On Windows, also check Add/Remove Programs or the registry under HKLM\SOFTWARE\RealNetworks for installed RealPlayer components.
    Affected if RealPlayer is installed on the system
  2. Identify the installed RealPlayer version
    Open RealPlayer and navigate to Help > About RealPlayer to view the exact version number. Alternatively, locate the version information in the installer executable or the application's properties window (right-click the executable > Properties > Details).
    Affected if The installed version matches one of the affected versions: 14.0.0 through 14.0.7, 11.0, 11.0.1 for RealPlayer; or 1.0.0, 1.0.1, 1.0.2, 1.0.5, 1.1, 1.1.1 through 1.1.5 for RealPlayer SP
  3. Verify RV10 codec module presence
    Locate the RealVideo codec files within the RealPlayer installation directory. The RV10 codec is typically distributed as a DLL such as RV10vfw.dll, Ivrend.dll, or similar RealVideo encoder/decoder modules. Search the installation folder for files containing 'rv10' in the filename.
    Affected if The RV10 codec module exists in the RealPlayer installation directory and is available for loading
  4. Confirm codec can be invoked
    Check if RealPlayer or the RV10 codec is registered as an available video codec on the system. On Windows, this can be verified by attempting to play a RealVideo file (.rv, .rm, .rmvb) or checking codec enumeration tools. The vulnerability triggers when RealPlayer processes a crafted video stream using the RV10 decoder.
    Affected if RealPlayer can process RealVideo content and the RV10 decoder is active or can be activated when opening a crafted video file

The system is affected if RealPlayer or RealPlayer SP is installed with a version matching the affected list and the RV10 RealVideo codec module is present and capable of being invoked.

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 to RealPlayer 15.02.71 or later; until patched, restrict or disable RealPlayer and warn users against opening untrusted RealVideo content.

Recommended fix Moderate confidence

RealPlayer 15.0.2.71 or later; RealPlayer SP 1.1.6 or later

  1. Upgrade to RealPlayer 15.0.2.71 or later, which contains the fix for the RV10 codec height/width handling vulnerability
  2. If RealPlayer SP is used, upgrade to a version newer than 1.1.5
  3. Verify the installed version by checking Help > About RealPlayer
  4. Download the update from the official RealNetworks service portal or trusted software distribution channels
Caveat RealPlayer has been discontinued by RealNetworks; ensure compatibility with your operating system before upgrading

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

Fix this in Realplayer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing2.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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