CVE-2007-0064
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 · uneditedHeap-based buffer overflow in Windows Media Format Runtime 7.1, 9, 9.5, 9.5 x64 Edition, 11, and Windows Media Services 9.1 for Microsoft Windows 2000, XP, Server 2003, and Vista allows user-assisted remote attackers to execute arbitrary code via a crafted Advanced Systems Format (ASF) 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 confidenceHeap-based buffer overflow in Windows Media Format Runtime allows remote code execution via crafted ASF (Advanced Systems Format) files. The vulnerability affects versions 7.1, 9, 9.5, 9.5 x64, and 11 of Windows Media Format Runtime, as well as Windows Media Services 9.1, across Windows 2000, XP, Server 2003, and Vista.
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= 7.1= 9= 9.5= 11= 9.1CVSS 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.
-
Identify Windows Media Format Runtime versionCheck the version of wmformat.dll in the system directory (typically C:\Windows\System32\wmformat.dll) by right-clicking the file, selecting Properties, and viewing the Version tab. Alternatively, open Command Prompt and run: dir C:\Windows\System32\wmformat.dllAffected if The reported file version is 7.1.x, 9.0.x, 9.5.x, or 11.x (or 9.5 x64 variant)
-
Verify Windows Media Services versionOpen Control Panel, go to Add or Remove Programs (or Programs and Features), and look for 'Windows Media Services' in the list of installed programs. Note the version shown.Affected if Windows Media Services version 9.1 is installed
-
Confirm Windows operating system versionOpen Command Prompt and run: winver or right-click My Computer and select Properties to view the Windows edition and version.Affected if The system is running Windows 2000, Windows XP, Windows Server 2003, or Windows Vista
-
Check if Windows Media Format Runtime is actively handling ASF filesAttempt to play a standard ASF file using Windows Media Player, or check file associations for .asf files in the registry under HKEY_CLASSES_ROOT\.asf to confirm the runtime is registered and functional.Affected if ASF files are associated and playable through the Windows Media Format Runtime component
You are affected if Windows Media Format Runtime versions 7.1, 9, 9.5, or 11 is installed on Windows 2000/XP/Server 2003/Vista, or if Windows Media Services 9.1 is present, and the system can process ASF media files.
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.
From vendor dataApply the relevant Microsoft security update (MS07-068) to patch the vulnerability. If immediate patching is not feasible, disable Windows Media Format Runtime or implement application whitelisting to block execution of untrusted ASF files.
- 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-2007-0064 — 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-2007-0064 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