Google Android up to 9.0 Email Attachment ComposeActivityEmailExternal.java ComposeActivityEmailExternal information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Google Android 7.1.1/7.1.2/8.0/8.1/9.0. Impacted is the function ComposeActivityEmailExternal of the file ComposeActivityEmailExternal.java of the component Email Attachment Handler. The manipulation leads to information disclosure.
This vulnerability is documented as CVE-2019-2124. The attack needs to be performed locally. There is not any exploit available.
It is recommended to apply a patch to fix this issue.
Details
A vulnerability, which was classified as problematic, has been found in Google Android 7.1.1/7.1.2/8.0/8.1/9.0 (Smartphone Operating System). This issue affects the function ComposeActivityEmailExternal of the file ComposeActivityEmailExternal.java of the component Email Attachment Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
In ComposeActivityEmailExternal of ComposeActivityEmailExternal.java in Android 7.1.1, 7.1.2, 8.0, 8.1 and 9, there is a possible way to silently attach files to an email due to a confused deputy. This could lead to local information disclosure.
The weakness was released 09/05/2019. The identification of this vulnerability is CVE-2019-2124 since 12/10/2018. The exploitation is known to be easy. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Applying a patch is able to eliminate this problem.
Entries connected to this vulnerability are available at VDB-141315, VDB-141314, VDB-141313 and VDB-141312. Be aware that VulDB is the high quality source for 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: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
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: Partially
Local: Yes
Remote: No
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
12/10/2018 🔍09/05/2019 🔍
09/06/2019 🔍
12/13/2023 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
CVE: CVE-2019-2124 (🔍)
GCVE (CVE): GCVE-0-2019-2124
GCVE (VulDB): GCVE-100-141311
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/06/2019 13:20Updated: 12/13/2023 11:17
Changes: 09/06/2019 13:20 (40), 08/13/2020 10:55 (18), 12/13/2023 11:17 (4)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.