CVE-2008-6775
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 · uneditedHTC Touch Pro and HTC Touch Cruise vCard allows remote attackers to cause denial of service (CPU consumption, SMS consumption, and connectivity loss) via a flood of vCards to UDP port 9204.
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 confidenceThe HTC Touch Pro and HTC Touch Cruise smartphones contain a vulnerability in their vCard handling component. Remote attackers can cause denial of service by sending a flood of malicious vCards to UDP port 9204, resulting in excessive CPU consumption, SMS consumption, and complete loss of network connectivity.
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 dataall versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:N/C:N/I:N/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 the device modelCheck the device settings or boot screen to confirm the exact model (Htc Touch Cruise or Htc Touch Pro)Affected if The device is an HTC Touch Cruise or HTC Touch Pro with any firmware version
-
Confirm UDP port 9204 is listeningUse network scanning tools (such as netstat or network port scanners compatible with Windows Mobile) to check if UDP port 9204 is open and listening on the deviceAffected if UDP port 9204 is open and accepting traffic on the device
-
Check for vCard processing enabledInspect the device contacts/address book application settings to determine if vCard import/processing functionality is enabled or was recently usedAffected if vCard handling is enabled or was activated, allowing incoming vCard data to be processed
-
Monitor for attack symptomsObserve the device for signs of excessive CPU usage, unusual SMS activity spikes, or complete loss of network connectivity, especially after receiving unexpected data on port 9204Affected if Device exhibits sudden high CPU consumption, excessive SMS messages sent/received, or complete loss of network connectivity without other explanation
-
Inspect network traffic on port 9204Use packet capture tools on the network to monitor UDP traffic on port 9204 for suspicious or malformed vCard data being sent to the deviceAffected if Unsolicted or malformed vCard data is being received on UDP port 9204
A user is affected if they own an HTC Touch Cruise or HTC Touch Pro device with any firmware version, and that device is receiving unsolicited vCard data on UDP port 9204, resulting in resource exhaustion or connectivity loss.
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 vendor firmware updates to affected devices if available, or implement network-level filtering to block unsolicited UDP traffic on port 9204.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-6775 — 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-6775 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