| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 4.1. It has been rated as problematic. This issue affects some unknown processing of the component Clipboard Access. Performing a manipulation results in information disclosure. Additionally, an exploit exists. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in Google Android 4.1 (Smartphone Operating System). This affects an unknown function of the component Clipboard Access. 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 weakness was released 03/14/2013 by Jann Horn as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The public release happened without involvement of Google. Technical details are unknown but a private exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
It is declared as proof-of-concept.
Upgrading to version 4.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (91278†). Entries connected to this vulnerability are available at VDB-7999, VDB-8008, VDB-8000 and VDB-8002. 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: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.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: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Private
Status: Proof-of-Concept
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 4.2
Timeline
03/14/2013 🔍03/18/2013 🔍
05/04/2018 🔍
Sources
Vendor: google.comAdvisory: seclists.org
Researcher: Jann Horn
Status: Not defined
GCVE (VulDB): GCVE-100-8001
OSVDB: 91278
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/18/2013 07:55Updated: 05/04/2018 09:10
Changes: 03/18/2013 07:55 (45), 05/04/2018 09:10 (2)
Complete: 🔍
Committer:
Cache ID: 216:81D: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.