NLL com.nll.cb up to 0.330-playStore-NoAccessibility-arm8 on Android com.nll.cb.dialer.dialer.DialerActivity permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in NLL com.nll.cb up to 0.330-playStore-NoAccessibility-arm8 on Android. Affected is an unknown function of the component com.nll.cb.dialer.dialer.DialerActivity. This manipulation causes permission. This vulnerability appears as CVE-2024-36064. The attack requires local access. There is no available exploit.
Details
A vulnerability has been found in NLL com.nll.cb up to 0.330-playStore-NoAccessibility-arm8 on Android and classified as problematic. Affected by this vulnerability is some unknown processing of the component com.nll.cb.dialer.dialer.DialerActivity. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect integrity. The summary by CVE is:
The NLL com.nll.cb (aka ACR Phone) application through 0.330-playStore-NoAccessibility-arm8 for Android allows any installed application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.nll.cb.dialer.dialer.DialerActivity component.
The advisory is shared at github.com. This vulnerability is known as CVE-2024-36064 since 05/19/2024. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
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: PermissionCWE: CWE-275 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/19/2024 🔍11/08/2024 🔍
11/08/2024 🔍
11/08/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-36064 (🔍)
GCVE (CVE): GCVE-0-2024-36064
GCVE (VulDB): GCVE-100-283513
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 11/08/2024 07:33Changes: 11/08/2024 07:33 (55)
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.