dbcve.org
Windows 2003 ServerOperating system · Microsoft

CVE-2006-6902

HIGH · 10.0 CVSS v2.0 Published 2006-12-31
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
Unspecified vulnerability in the Bluetooth stack in Microsoft Windows Mobile Pocket PC edition allows remote attackers to gain administrative access (aka Remote Root) via unspecified vectors.

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

Vulnerability in the Bluetooth stack of Microsoft Windows Mobile Pocket PC edition enables remote attackers to achieve administrative (root) access through unspecified attack vectors. The exact exploitation method and technical details are not disclosed in available sources.

MitigationDisable Bluetooth on affected Windows Mobile devices if not required; otherwise isolate affected devices from untrusted networks and consider retiring these legacy devices as no patches are available for this discontinued OS.

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 2003 ServerOperating system
Affected:= mobile_pocket_pc

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the operating system
    Check if the device is running Windows Mobile Pocket PC edition. On the device, go to Settings > About to view the OS version and confirm it shows Windows Mobile Pocket PC.
    Affected if The device is running Windows Mobile Pocket PC edition from the affected era (early 2000s)
  2. Locate Bluetooth configuration
    On Windows Mobile Pocket PC, navigate to Settings > Bluetooth. Check if the Bluetooth control panel applet exists and is accessible.
    Affected if Bluetooth control panel applet is present on the device
  3. Determine if Bluetooth is enabled
    In the Bluetooth settings panel, check the status indicator or toggle to see if Bluetooth radio is currently turned on.
    Affected if Bluetooth is currently enabled and active on the device
  4. Check Bluetooth stack visibility
    Check if the Bluetooth icon appears in the system tray or status bar of the Windows Mobile device, indicating the stack is loaded and running.
    Affected if Bluetooth stack is loaded and running (icon visible in system tray)
  5. Assess network exposure
    Determine if the device has been used on untrusted networks, cellular data, or paired with unknown Bluetooth devices. Review any connection logs if available.
    Affected if The device has Bluetooth enabled and has been used on untrusted networks or paired with unknown devices

A defender is affected if the device runs Windows Mobile Pocket PC edition with the Bluetooth stack enabled and accessible, especially if used on untrusted networks, as no patches exist for this discontinued OS.

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

Disable Bluetooth on affected Windows Mobile devices if not required; otherwise isolate affected devices from untrusted networks and consider retiring these legacy devices as no patches are available for this discontinued OS.

Recommended fix Moderate confidence
  1. Disable Bluetooth on the Windows Mobile Pocket PC device if not required for business operations
  2. If Bluetooth is required, limit visibility of the device by setting it to 'non-discoverable' mode
  3. Do not accept unexpected or unknown Bluetooth pairing requests
  4. Consider migrating to a supported mobile operating system as Windows Mobile is end-of-life
Caveat Disabling Bluetooth may impact legitimate business use cases requiring wireless connectivity

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 2003 Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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