CVE-2012-2217
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 · uneditedThe HTC IQRD service for Android on the HTC EVO 4G before 4.67.651.3, EVO Design 4G before 2.12.651.5, Shift 4G before 2.77.651.3, EVO 3D before 2.17.651.5, EVO View 4G before 2.23.651.1, Vivid before 3.26.502.56, and Hero does not restrict localhost access to TCP port 2479, which allows remote attackers to (1) send SMS messages, (2) obtain the Network Access Identifier (NAI) and its password, or trigger (3) popup messages or (4) tones via a crafted application that leverages the android.permission.INTERNET permission.
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 IQRD service on multiple HTC Android devices exposes TCP port 2479 without restricting localhost access, allowing any application with INTERNET permission to communicate with this service and perform privileged actions including sending SMS, retrieving NAI credentials, and triggering popups/tones.
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<= 4.54.651.1= 1.32.651.1= 1.47.651.1= 3.26.651.6= 3.29.651.5= 3.30.651.2= 3.30.651.3= 3.70.651.1= 4.22.651.2= 4.24.651.1= 4.53.651.1all versions= gri40<= 1.19.651.1= 1.19.651.0all versions<= 2.76.651.6= 1.17.651.1= 2.75.651.4= 2.75.651.5all versions<= 2.08.651.3= 1.11.651.3= 1.13.651.7= 2.08.651.2all versions= gri40CVSS 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
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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 HTC device modelCheck the device model in Settings > About Phone or run 'getprop ro.product.device'Affected if The model is not Evo 4g, Evo Design 4g, Shift 4g, or Evo 3d (these are the affected models)
-
Check the software versionLocate the firmware/software version in Settings > About Phone > Software version or run 'getprop ro.build.version.incremental'Affected if The installed version matches or is below any of the affected version ranges listed for the specific device model
-
Verify port 2479 is listeningRun 'netstat -an | grep 2479' or 'ss -tlnp | grep 2479' to check if the IQRD service port is openAffected if Port 2479 is shown as LISTEN on the device, indicating the vulnerable service is active
The device is affected if it is an HTC Evo 4g, Evo Design 4g, Shift 4g, or Evo 3d running a software version within the affected ranges AND port 2479 is listening.
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 dataUpdate affected HTC devices to the specified firmware versions (EVO 4G: 4.67.651.3, EVO Design 4G: 2.12.651.5, Shift 4G: 2.77.651.3, EVO 3D: 2.17.651.5, EVO View 4G: 2.23.651.1, Vivid: 3.26.502.56) that contain the fix.
- 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-2012-2217 — 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-2012-2217 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