| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Samsung Galaxy S. It has been declared as critical. This impacts an unknown function of the component dmesg Buffer. Such manipulation leads to credentials management. This vulnerability is documented as CVE-2012-2980. Additionally, an exploit exists. A patch should be applied to remediate this issue.
Details
A vulnerability was found in Samsung Galaxy S (Smartphone Operating System) (version now known) and classified as critical. Affected by this issue is some unknown processing of the component dmesg Buffer. The manipulation with an unknown input leads to a credentials management vulnerability. Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality. CVE summarizes:
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.
The weakness was released 08/16/2012 by Glenn ten Cate as VU#251635 as not defined bulletin (Website). The advisory is available at kb.cert.org. The public release was coordinated with the vendor. This vulnerability is handled as CVE-2012-2980 since 05/30/2012. Local access is required to approach this attack. Required for exploitation is a simple authentication. Technical details are unknown but a private exploit is available. This vulnerability is assigned to T1552 by the MITRE ATT&CK project. This issue is triggered when the device stores touch coordinates in the dmesg buffer.
It is declared as proof-of-concept. An attacker may gain access to potentially sensitive touch coordinate information with a specially crafted application.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at OSVDB (84925†). kb.cert.org is providing further details. Entry connected to this vulnerability is available at VDB-6025. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.5
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Credentials managementCWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Private
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
05/30/2012 🔍08/16/2012 🔍
08/21/2012 🔍
08/29/2012 🔍
08/10/2024 🔍
Sources
Vendor: samsung.comAdvisory: VU#251635
Researcher: Glenn ten Cate
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2012-2980 (🔍)
GCVE (CVE): GCVE-0-2012-2980
GCVE (VulDB): GCVE-100-6026
CERT: 🔍
OSVDB: 84925
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍
Entry
Created: 08/29/2012 12:19Updated: 08/10/2024 19:19
Changes: 08/29/2012 12:19 (54), 04/29/2018 10:30 (6), 08/10/2024 19:19 (17)
Complete: 🔍
Cache ID: 216:A38:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.