Google Android up to 4.2 diagchar_core.c memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.3$25k-$100k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Android. Affected by this vulnerability is an unknown functionality of the file diagchar_core.c. This manipulation causes memory corruption. This vulnerability is registered as CVE-2012-4220. No exploit is available.

Detailsinfo

A vulnerability has been found in Google Android (Smartphone Operating System) and classified as critical. Affected by this vulnerability is an unknown functionality of the file diagchar_core.c. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

diagchar_core.c in the Qualcomm Innovation Center (QuIC) Diagnostics (aka DIAG) kernel-mode driver for Android 2.3 through 4.2 allows attackers to execute arbitrary code or cause a denial of service (incorrect pointer dereference) via an application that uses crafted arguments in a local diagchar_ioctl call.

The weakness was published 11/30/2012 as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. This vulnerability is known as CVE-2012-4220 since 08/08/2012. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 08/11/2024). It is expected to see the exploit prices for this product increasing in the near future.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (80498), SecurityFocus (BID 56855†) and Vulnerability Center (SBV-47709†). Similar entries are available at VDB-63087 and VDB-63086. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/08/2012 🔍
11/15/2012 +99 days 🔍
11/30/2012 +15 days 🔍
11/30/2012 +0 days 🔍
12/07/2012 +7 days 🔍
12/21/2014 +744 days 🔍
03/24/2015 +93 days 🔍
08/11/2024 +3428 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: kb.cert.org
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2012-4220 (🔍)
GCVE (CVE): GCVE-0-2012-4220
GCVE (VulDB): GCVE-100-63085
CERT: 🔍
X-Force: 80498
SecurityFocus: 56855 - Qualcomm Android kernel Remote Code Execution and Denial of Service Vulnerabilities
Vulnerability Center: 47709 - Google Android 2.3 - 4.2 \x27kernel-mode\x27 Driver Remote Code Execution or DoS Vulnerability - CVE-2012-4220, Medium

scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍

Entryinfo

Created: 03/24/2015 12:22
Updated: 08/11/2024 13:25
Changes: 03/24/2015 12:22 (57), 06/16/2017 04:12 (4), 08/11/2024 13:25 (17)
Complete: 🔍
Cache ID: 216:370:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!