Windows Media PlayerApplication · Microsoft

CVE-2002-0372

HIGH · 7.5 CVSS v2.0 Published 2002-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Microsoft Windows Media Player versions 6.4 and 7.1 and Media Player for Windows XP allow remote attackers to bypass Internet Explorer's (IE) security mechanisms and run code via an executable .wma media file with a license installation requirement stored in the IE cache, aka the "Cache Path Disclosure via Windows Media Player".

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 · moderate confidence

This vulnerability in Windows Media Player 6.4, 7.1, and XP allows remote attackers to bypass Internet Explorer security restrictions by embedding executable content within .wma media files that include a license installation requirement. When these files are cached by IE, the license installation process can be manipulated to execute arbitrary code without proper security prompts.

MitigationApply the relevant Microsoft security patches from 2002 for Windows Media Player and IE, or upgrade to patched versions of Windows Media Player and Internet Explorer. Consider disabling automatic license installation for media files as a temporary workaround.

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 PlayerApplication
Affected:all versions= 6.4= 7.1

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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 Media Player version
    Open Windows Media Player, go to Help > About, or check the version via file properties of wmplayer.exe in Program Files/Windows Media Player
    Affected if Version is 6.4 or 7.1 (or Windows Media Player for XP if still on original unpatched version)
  2. Verify Internet Explorer security zone settings
    In IE, go to Internet Options > Security > Custom Level, look for settings related to 'Initialize and script ActiveX controls not marked as safe' and 'Download signed ActiveX controls'
    Affected if Security zones are set to allow ActiveX controls or automatic license installation without prompts
  3. Confirm license installation is enabled for media files
    In IE, go to Internet Options > Security > Custom Settings for each zone, search for 'License acquisition' or 'Automatic component download' related to media content
    Affected if License installation is allowed without user prompt in the affected security zone
  4. Check for cached .wma media files
    Examine IE cache folder (typically %Temporary Internet Files% or %Local AppData%\Microsoft\Windows\INetCache) for .wma files that may contain embedded license requirements
    Affected if Untrusted .wma files with license installation requirements have been cached by IE

A user is affected if they run an unpatched Windows Media Player 6.4 or 7.1 with IE security settings that permit automatic license installation for media files, and have cached or opened .wma files containing malicious license requirements.

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 the relevant Microsoft security patches from 2002 for Windows Media Player and IE, or upgrade to patched versions of Windows Media Player and Internet Explorer. Consider disabling automatic license installation for media files as a temporary workaround.

Fix this in Windows Media Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-0372 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-0372 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