com.full.dialer.top.secure.encrypted up to 1.0.1 on Android Phone Call permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in com.full.dialer.top.secure.encrypted up to 1.0.1 on Android. This affects an unknown part of the component Phone Call Handler. Performing a manipulation results in permission. This vulnerability was named CVE-2023-42469. The attack needs to be approached locally. In addition, an exploit is available.
Details
A vulnerability was found in com.full.dialer.top.secure.encrypted up to 1.0.1 on Android (Android App Software). It has been classified as critical. This affects some unknown functionality of the component Phone Call Handler. The manipulation with an unknown input leads to a permission vulnerability. CWE is classifying the issue as CWE-275. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The com.full.dialer.top.secure.encrypted application through 1.0.1 for Android enables any installed application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.full.dialer.top.secure.encrypted.activities.DialerActivity component.
The weakness was presented 09/14/2023. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2023-42469 since 09/11/2023. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.
The exploit is shared for download at github.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-46909). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
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: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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/11/2023 🔍09/14/2023 🔍
09/14/2023 🔍
02/02/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-42469 (🔍)
GCVE (CVE): GCVE-0-2023-42469
GCVE (VulDB): GCVE-100-239703
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 09/14/2023 07:51Updated: 02/02/2026 11:53
Changes: 09/14/2023 07:51 (42), 10/11/2023 17:06 (11), 02/02/2026 11:53 (16)
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.