# CVE-2011-4872: Information disclosure in n/a

> A malicious app with Wi-Fi state permission can expose 802.1X credentials and SSID on multiple HTC Android devices.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Feb 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2wx5-pg32-77vx

## What is CVE-2011-4872?

CVE-2011-4872 is a low-severity vulnerability in n/a, published on 5 Feb 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple HTC Android devices including Desire HD FRG83D and GRI40, Glacier FRG83, Droid Incredible FRF91, Thunderbolt 4G FRG83D, Sensation Z710e GRI40, Sensation 4G GRI40, Desire S GRI40, EVO 3D GRI40, and EVO 4G GRI40 allow remote attackers to obtain 802.1X Wi-Fi credentials and SSID via a crafted application that uses the android.permission.ACCESS_WIFI_STATE permission to call the toString method on the WifiConfiguration class.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2011-4872?

It affects 9 products.


Products: Htc Desire Hd, Htc Desire S, Htc Droid Incredible, Htc Evo 3d, Htc Evo 4g, Htc Glacier, Htc Sensation 4g, Htc Sensation Z710e, Htc Thunderbolt 4g.

## How do I fix CVE-2011-4872?

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

## Is CVE-2011-4872 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4872 and fix it if it is affected.

What it is: CVE-2011-4872 is a low-severity vulnerability in n/a, published on 5 Feb 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-4872 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-2011-4872/ (Markdown: https://insights.sbomify.com/CVE-2011-4872/index.md)
```

## Sources

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

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