Google Android 2.3/2.3.3/2.3.4/2.3.5 Bluetooth information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 2.3/2.3.3/2.3.4/2.3.5. It has been classified as problematic. This issue affects some unknown processing of the component Bluetooth. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2011-4276. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Google Android 2.3/2.3.3/2.3.4/2.3.5 (Smartphone Operating System). It has been classified as problematic. This affects an unknown code block of the component Bluetooth. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
The Bluetooth service (com/android/phone/BluetoothHeadsetService.java) in Android 2.3 before 2.3.6 allows remote attackers within Bluetooth range to obtain contact data via an AT phonebook transfer.
The weakness was shared 01/25/2012 as 21347 (Website). The advisory is shared at code.google.com. This vulnerability is uniquely identified as CVE-2011-4276 since 11/03/2011. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 2.3.5 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (72732), SecurityFocus (BID 51709†) and Vulnerability Center (SBV-36971†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Android 2.3.5
Timeline
10/28/2011 🔍11/03/2011 🔍
01/25/2012 🔍
01/25/2012 🔍
01/27/2012 🔍
11/06/2012 🔍
03/23/2015 🔍
04/20/2017 🔍
Sources
Vendor: google.comAdvisory: 21347
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2011-4276 (🔍)
GCVE (CVE): GCVE-0-2011-4276
GCVE (VulDB): GCVE-100-60009
X-Force: 72732
SecurityFocus: 51709 - Android Bluetooth Stack Contact Information Disclosure Vulnerability
Vulnerability Center: 36971 - Android 2.3-2.3.5 Remote Leakage of Sensitive Information, Medium
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/23/2015 16:50Updated: 04/20/2017 14:12
Changes: 03/23/2015 16:50 (59), 04/20/2017 14:12 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.