LG V60 Thin Q 5G onActivityResult improper export of android application components
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in LG V60 Thin Q 5G. This affects the function onActivityResult. This manipulation causes improper export of android application components.
The identification of this vulnerability is CVE-2023-44129. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability classified as problematic was found in LG V60 Thin Q 5G (version now known). Affected by this vulnerability is the function onActivityResult. The manipulation with an unknown input leads to a improper export of android application components vulnerability. The CWE definition for the vulnerability is CWE-926. The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains. As an impact it is known to affect confidentiality. The summary by CVE is:
The vulnerability is that the Messaging ("com.android.mms") app patched by LG forwards attacker-controlled intents back to the attacker in the exported "com.android.mms.ui.QClipIntentReceiverActivity" activity. The attacker can abuse this functionality by launching this activity and then sending a broadcast with the "com.lge.message.action.QCLIP" action. The attacker can send, e.g., their own data/clipdata and set Intent.FLAG_GRANT_* flags. After the attacker received that intent in the "onActivityResult()" method, they would have access to arbitrary content providers that have the `android:grantUriPermissions="true"` flag set.
The weakness was shared 09/27/2023. The advisory is shared at lgsecurity.lge.com. This vulnerability is known as CVE-2023-44129 since 09/26/2023. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/20/2023).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.4VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
NVD Vector: 🔍
CNA Base Score: 3.6
CNA Vector (LG Electronics): 🔍
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: Improper export of android application componentsCWE: CWE-926
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/26/2023 🔍09/27/2023 🔍
09/27/2023 🔍
10/20/2023 🔍
Sources
Advisory: lgsecurity.lge.comStatus: Confirmed
CVE: CVE-2023-44129 (🔍)
GCVE (CVE): GCVE-0-2023-44129
GCVE (VulDB): GCVE-100-240589
Entry
Created: 09/27/2023 18:48Updated: 10/20/2023 09:05
Changes: 09/27/2023 18:48 (45), 10/20/2023 09:05 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.