# CVE-2012-2217: Missing authorization in n/a

> Remote attackers can send SMS, steal credentials, or trigger UI elements via a malicious app exploiting unrestricted localhost access in HTC IQRD service.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w7x7-pv7g-c83h

## What is CVE-2012-2217?

CVE-2012-2217 is a medium-severity missing authorization vulnerability in n/a, published on 1 May 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2012-2217?

It affects 14 products.


Products: Htc Evo 3d, Htc Evo 3d Software, Htc Evo 4g, Htc Evo 4g Software, Htc Evo Design 4g, Htc Evo Design 4g Software, Htc Evo View 4g, Htc Evo View 4g Software, Htc Hero, Htc Hero Software, Htc Shift 4g, Htc Shift 4g Software, Htc Vivid, Htc Vivid Software.

## How do I fix CVE-2012-2217?

No fix has been published for CVE-2012-2217 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-2217 being exploited?

There is no known exploitation of CVE-2012-2217 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2217 and fix it if it is affected.

What it is: CVE-2012-2217 is a medium-severity missing authorization vulnerability in n/a, published on 1 May 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-2217 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-2217/ (Markdown: https://insights.sbomify.com/CVE-2012-2217/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2217
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2217
- OSV: https://osv.dev/vulnerability/CVE-2012-2217

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-2217/
Summaries are generated and may contain mistakes; the official description above is the record.