Droid IncredibleHardware / appliance · Htc

CVE-2013-4622

HIGH · 7.5 CVSS v2.0 Published 2013-06-19
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
The 3G Mobile Hotspot feature on the HTC Droid Incredible has a default WPA2 PSK passphrase of 1234567890, which makes it easier for remote attackers to obtain access by leveraging a position within the WLAN coverage area.

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 confidence

The HTC Droid Incredible's 3G Mobile Hotspot feature ships with a hardcoded default WPA2 PSK passphrase of '1234567890', allowing attackers within WLAN range to easily authenticate to the hotspot and intercept traffic or pivot into the connected network.

MitigationChange the default WPA2 PSK passphrase to a strong, unique password via the hotspot settings, and ensure users are informed of the importance of changing defaults before deploying mobile hotspot functionality.

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
Droid IncredibleHardware / appliance
Affected:all versions= frf91

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 the device model
    Check if the device is an HTC Droid Incredible by viewing the device information in Settings > About Phone > Model Number
    Affected if The device model is HTC Droid Incredible (frf91)
  2. Check if 3G Mobile Hotspot is enabled
    Navigate to Settings > Wireless & Networks > Mobile Hotspot (or Settings > Network & Internet > Hotspot & Tethering) and verify if the mobile hotspot toggle is turned on
    Affected if The 3G Mobile Hotspot feature is currently enabled
  3. Inspect the configured WPA2 PSK passphrase
    In the mobile hotspot settings, view the current WPA2 PSK passphrase. On the Droid Incredible, this is typically found under Mobile Hotspot settings > Configure > Security password field
    Affected if The configured WPA2 PSK passphrase is '1234567890' (the hardcoded default)

A user is affected if they are using an HTC Droid Incredible with the 3G Mobile Hotspot enabled and the WPA2 PSK passphrase is still set to the default value '1234567890'.

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

Change the default WPA2 PSK passphrase to a strong, unique password via the hotspot settings, and ensure users are informed of the importance of changing defaults before deploying mobile hotspot functionality.

Fix this in Droid Incredible Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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