dbcve.org
RealplayerApplication · Realnetworks

CVE-2012-0924

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
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 vectors involving a VIDOBJ_START_CODE code in a header within a 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

RealNetworks RealPlayer versions 11.x, 14.x, 15.x before 15.02.71, and RealPlayer SP 1.0-1.1.5 contain a memory corruption vulnerability in video stream parsing that allows remote arbitrary code execution via a crafted VIDOBJ_START_CODE in a video header.

MitigationUpdate RealPlayer to version 15.02.71 or later; if the software is end-of-life and no patch is available, uninstall RealPlayer or block it via application controls.

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. Locate RealPlayer installation
    Search for RealPlayer executables: check C:\Program Files\Real\RealPlayer or C:\Program Files (x86)\Real\RealPlayer on Windows; check /Applications/RealPlayer on macOS; check ~/.local/share/realplayer or /usr/bin/realplayer on Linux
    Affected if RealPlayer executable is found on the system
  2. Determine installed version
    Right-click the RealPlayer.exe file, select Properties, and view the Version tab. Alternatively, open RealPlayer, go to Help > About RealPlayer to display the version number
    Affected if Version displayed is 11.0, 11.0.1, any 14.x version (14.0.0 through 14.0.7), or RealPlayer SP 1.0.0 through 1.1.5, or any 15.x version below 15.02.71
  3. Confirm video playback capability
    Open RealPlayer and verify that video playback features are available. Check if the video codec/parsing module is loaded by viewing Tools > Preferences > Hardware or About > Plugins
    Affected if Video playback features are enabled and the video parsing component is active
  4. Compare version against safe threshold
    If version is 15.x, verify the full version number is 15.02.71 or higher. Versions below this threshold in the 15.x line are vulnerable
    Affected if Installed version is 15.x but below 15.02.71

The system is affected if RealPlayer is installed and the version is 11.x, 14.x, 15.x before 15.02.71, or SP 1.0-1.1.5, with video playback capability enabled.

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; if the software is end-of-life and no patch is available, uninstall RealPlayer or block it via application controls.

Recommended fix High confidence

RealPlayer 15.0.2.71 or later (RealPlayer SP should be updated to the latest available version)

  1. 1. Uninstall the current version of RealPlayer or RealPlayer SP from the system
  2. 2. Download RealPlayer version 15.0.2.71 or later from the official RealNetworks website (service.real.com)
  3. 3. Verify the installer file integrity using checksums if available
  4. 4. Install the updated RealPlayer version
  5. 5. Restart any running RealPlayer instances if the upgrade was performed in-place
Caveat RealPlayer is discontinued software; ensure any legacy media workflows are compatible with the newer version or consider migrating to alternative media players

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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