CVE-2008-3010
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 · uneditedMicrosoft Windows Media Player 6.4, Windows Media Format Runtime 7.1 through 11, and Windows Media Services 4.1 and 9 incorrectly associate ISATAP addresses with the Local Intranet zone, which allows remote servers to capture NTLM credentials, and execute arbitrary code through credential-reflection attacks, by sending an authentication request, aka "ISATAP 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 confidenceWindows Media Player and Windows Media Services incorrectly classify ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) addresses as belonging to the Local Intranet zone instead of the Internet zone. This misclassification causes the system to send NTLM credentials automatically during authentication attempts, allowing remote attackers to capture these credentials and perform credential-reflection attacks to execute arbitrary code.
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= 6.4CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Check Windows Media Player versionOpen Windows Media Player, go to Help > About Windows Media Player. The version number is displayed there.Affected if The installed version is exactly 6.4 (9.0.0.6.4)
-
Check if ISATAP tunneling is enabledRun 'netsh interface isatap show state' from an elevated command prompt to display ISATAP interface status.Affected if ISATAP state shows as enabled or the ISATAP tunnel adapter is present in 'ipconfig /all' output
-
Verify ISATAP router is configuredRun 'netsh interface isatap show router' to check if an ISATAP router address is configured.Affected if A router address is configured and reachable, indicating ISATAP is actively in use
-
Check NTLM authentication settingsReview group policy settings under Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options for 'Network security: LAN Manager authentication level'.Affected if Authentication level is set to 'Send NTLM response only' or lower (allows NTLM credential transmission)
A system is affected if Windows Media Player 6.4 is installed, ISATAP is enabled/active on the network, and NTLM authentication is permitted, allowing automatic credential submission to ISATAP addresses.
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 (MS08-076) to affected Windows Media components. Additionally, consider disabling NTLM authentication or implementing EPA (Extended Protection Authentication) to mitigate credential theft attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3010 — 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-2008-3010 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