I-Funbox iFunbox 4.2 Apple Mobile Device Service unquoted search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in I-Funbox iFunbox 4.2. Affected is an unknown function of the component Apple Mobile Device Service. This manipulation causes unquoted search path. This vulnerability is handled as CVE-2021-47803. It is possible to launch the attack on the local host. Additionally, an exploit exists.
Details
A vulnerability classified as critical was found in I-Funbox iFunbox 4.2. Affected by this vulnerability is an unknown functionality of the component Apple Mobile Device Service. The manipulation with an unknown input leads to a unquoted search path vulnerability. The CWE definition for the vulnerability is CWE-428. The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
iFunbox 4.2 contains an unquoted service path vulnerability in the Apple Mobile Device Service that allows local attackers to execute code with elevated privileges. Attackers can insert a malicious executable into the unquoted service path to run with LocalSystem privileges when the service restarts.
The weakness was released by Julio Aviña as 50040. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2021-47803 since 01/14/2026. The exploitation appears to be difficult. An attack has to be approached locally. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1574.009 for this issue.
It is possible to download the exploit at exploit-db.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 Exploit-DB (50040). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.0
VulDB Temp Score: 6.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (VulnCheck): 🔒
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: Unquoted search pathCWE: CWE-428 / CWE-426
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 |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
01/14/2026 CVE reserved01/16/2026 Advisory disclosed
01/16/2026 VulDB entry created
01/16/2026 VulDB entry last update
Sources
Advisory: 50040Researcher: Julio Aviña
Status: Not defined
CVE: CVE-2021-47803 (🔒)
GCVE (CVE): GCVE-0-2021-47803
GCVE (VulDB): GCVE-100-341461
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/16/2026 09:19Changes: 01/16/2026 09:19 (80)
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.