CVE-2012-2217: The 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…
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2% (FIRST EPSS); higher than 81.3% of all records.
- No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The 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.
- Published
- May 1, 2012
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 81th percentile
- CWE
- CWE-264
Report tools
Action score
26
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| htc | evo 4g software | cpe:2.3:a:htc:evo_4g_software |
| htc | evo 4g | cpe:2.3:h:htc:evo_4g |
| htc | evo design 4g software | cpe:2.3:a:htc:evo_design_4g_software |
| htc | evo design 4g | cpe:2.3:h:htc:evo_design_4g |
| htc | shift 4g software | cpe:2.3:a:htc:shift_4g_software |
| htc | shift 4g | cpe:2.3:h:htc:shift_4g |
| htc | evo 3d software | cpe:2.3:a:htc:evo_3d_software |
| htc | evo 3d | cpe:2.3:h:htc:evo_3d |
| htc | evo view 4g software | cpe:2.3:a:htc:evo_view_4g_software |
| htc | evo view 4g | cpe:2.3:h:htc:evo_view_4g |
| htc | vivid software | cpe:2.3:a:htc:vivid_software |
| htc | vivid | cpe:2.3:h:htc:vivid |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- htc evo 3dall versions
- htc evo 3dgri40
- htc evo 3d softwareup to 2.08.651.3 inclusive
- htc evo 3d software1.11.651.3
- htc evo 3d software1.13.651.7
- htc evo 3d software2.08.651.2
- htc evo 4gall versions
- htc evo 4ggri40
+12 more rows
- htc evo 4g softwareup to 4.54.651.1 inclusive
- htc evo 4g software1.32.651.1
- htc evo 4g software1.47.651.1
- htc evo 4g software3.26.651.6
- htc evo 4g software3.29.651.5
- htc evo 4g software3.30.651.2
- htc evo 4g software3.30.651.3
- htc evo 4g software3.70.651.1
- htc evo 4g software4.22.651.2
- htc evo 4g software4.24.651.1
- htc evo 4g software4.53.651.1
- htc evo design 4gall versions
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.