CVE-2012-2980: n/a vulnerability

CVE-2012-2980: The Samsung and HTC onTouchEvent method implementation for Android on the T-Mobile myTouch 3G Slide, HTC Me...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 16, 2024, 17:23 UTC (UTC+00:00)

Security readout for executives and security teams

This is a legacy Android information-leak issue. On specific HTC, T-Mobile, Sprint, AT&T, and Samsung devices, touch coordinates could be written into the kernel dmesg buffer. A malicious app could read those traces and infer sensitive user input such as PINs, phone numbers, or text messages. Exposure appears limited to the named 2012-era Android devices, including HTC myTouch/G2/Desire/ChaCha/EVO/Merge variants and Samsung Galaxy S. Modern fleets are likely exposed only if legacy or unmanaged devices remain in use. The bundle does not provide precise versions or CPE matching. Low to moderate for most organizations because the issue targets old device models. Escalate if the business still allows these devices to access messaging, authentication, or regulated data. The main action is inventory confirmation and retirement or vendor-guided remediation. Mitigation focus: Identify whether any named legacy Android devices remain in use.; Check HTC, Samsung, and carrier guidance before claiming a patch status.; Remove unsupported affected devices from sensitive workflows or managed fleets..

Prepared: Jun 28, 2026, 00:52 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2012-2980 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Aug 21, 2012, 10:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.