# CVE-2012-2980: Information disclosure in n/a

> A crafted application can read sensitive touch coordinates from the kernel log, exposing PINs and messages on specific Android devices.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Aug 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r7q2-c254-fg5v

## What is CVE-2012-2980?

CVE-2012-2980 is a high-severity vulnerability in n/a, published on 21 Aug 2012. 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

The Samsung and HTC onTouchEvent method implementation for Android on the T-Mobile myTouch 3G Slide, HTC Merge, Sprint EVO Shift 4G, HTC ChaCha, AT&T Status, HTC Desire Z, T-Mobile G2, T-Mobile myTouch 4G Slide, and Samsung Galaxy S stores touch coordinates in the dmesg buffer, which allows remote attackers to obtain sensitive information via a crafted application, as demonstrated by PIN numbers, telephone numbers, and text messages.

Weakness: CWE-255

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

It affects 9 products.


Products: Att Status, Htc Chacha, Htc Desire, Htc Merge, Samsung Galaxy S, Sprint Evo Shift 4g, T-Mobile G2, T-Mobile Mytouch 3g Slide, T-Mobile Mytouch 4g Slide.

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

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

## Is CVE-2012-2980 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2980 is a high-severity vulnerability in n/a, published on 21 Aug 2012. 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-2012-2980 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-2980/ (Markdown: https://insights.sbomify.com/CVE-2012-2980/index.md)
```

## Sources

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

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