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

> A malicious app can access sensitive phone number logs via a local TCP port in HTC's logging application, requiring user interaction to install the malicious app.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Oct 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pp8x-xmmj-hg66

## What is CVE-2011-3975?

CVE-2011-3975 is a low-severity vulnerability in Google Android, published on 3 Oct 2011. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A certain HTC update for Android 2.3.4 build GRJ22, when the Sense interface is used on the HTC EVO 3D, EVO 4G, ThunderBolt, and unspecified other devices, provides the HtcLoggers.apk application, which allows user-assisted remote attackers to obtain a list of telephone numbers from a log, and other sensitive information, by leveraging the android.permission.INTERNET application permission and establishing TCP sessions to 127.0.0.1 on port 65511 and a second port.

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

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

It affects 4 products.


Products: Google Android, Htc Evo 3d, Htc Evo 4g, Htc Thunderbolt.

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

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

## Is CVE-2011-3975 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3975 is a low-severity vulnerability in Google Android, published on 3 Oct 2011. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-3975 in the wild and no public exploit code.

Affected product: Google Android. 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-3975/ (Markdown: https://insights.sbomify.com/CVE-2011-3975/index.md)
```

## Sources

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

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