dbcve.org
Windows Media Format RuntimeApplication · Microsoft

CVE-2009-2499

HIGH · 8.5 CVSS v2.0 Published 2009-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Microsoft Windows Media Format Runtime 9.0, 9.5, and 11; and Microsoft Media Foundation on Windows Vista Gold, SP1, and SP2 and Server 2008; allows remote attackers to execute arbitrary code via an MP3 file with crafted metadata that triggers memory corruption, aka "Windows Media Playback Memory Corruption Vulnerability."

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

Memory corruption vulnerability in Windows Media Format Runtime and Microsoft Media Foundation allows remote code execution via specially crafted MP3 files with malicious metadata. The vulnerability affects Windows Media Format Runtime versions 9.0, 9.5, and 11, as well as Media Foundation on Windows Vista SP1/SP2 and Server 2008.

MitigationApply Microsoft security update MS09-047 to patch the vulnerability. Until patched, avoid opening MP3 files from untrusted sources and consider disabling Windows Media Player or using an alternative media player.

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
Windows Media Format RuntimeApplication
Affected:= 9.0= 9.5= 11
Windows 2000Operating system
Affected:all versions
Windows XpOperating system
Affected:all versions
Windows Server 2003Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions
Windows VistaOperating system
Affected:all versions
Windows Media ServicesApplication
Affected:= 9.1= 2008
Windows Media FoundationApplication
Affected:all versions

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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:S/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. Identify Windows version
    Run 'winver' or check system properties to determine the Windows version. Affected versions are Windows 2000, XP, Server 2003, Server 2008, and Vista.
    Affected if The system is running Windows 2000, XP, Server 2003, Server 2008, or Vista (any version).
  2. Check Windows Media Format Runtime version
    Locate wmvcore.dll in the system (typically in C:\Windows\System32 or C:\Windows\SysWOW64) and view its version properties. Alternatively, check 'Programs and Features' for Windows Media Format Runtime installation.
    Affected if Windows Media Format Runtime version 9.0, 9.5, or 11 is installed.
  3. Check Media Foundation version on Vista/Server 2008
    Locate mfcore.dll in C:\Windows\System32 and view its version properties. This component is present on Windows Vista and Windows Server 2008.
    Affected if Media Foundation is present (found on Windows Vista SP1/SP2 and Windows Server 2008).
  4. Verify Windows Media Player is installed
    Check if Windows Media Player is installed via 'Programs and Features' or by locating wmplayer.exe in the program files directory.
    Affected if Windows Media Player is installed and capable of playing MP3 files.
  5. Confirm MP3 file association with Windows Media Player
    Right-click any MP3 file, select Properties, and check the 'Opens with' field to see if Windows Media Player or Windows Media Foundation is set as the default handler.
    Affected if MP3 files are configured to open with Windows Media Player or the default media handler using the affected Media Foundation components.

A system is affected if it runs any of the listed Windows versions (2000 through Vista/Server 2008) and has Windows Media Format Runtime or Media Foundation installed with MP3 file handling 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security update MS09-047 to patch the vulnerability. Until patched, avoid opening MP3 files from untrusted sources and consider disabling Windows Media Player or using an alternative media player.

Fix this in Windows Media Format Runtime 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-2009-2499 — 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-2009-2499 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