Reolink App 4.54.0.4.20250526 on Android Setting public cloneable() method without final ('object hijack')
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Reolink App 4.54.0.4.20250526 on Android. It has been classified as problematic. This impacts an unknown function of the component Setting Handler. Performing a manipulation results in public cloneable() method without final ('object hijack'). This vulnerability is known as CVE-2025-55622. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability classified as problematic has been found in Reolink App 4.54.0.4.20250526 on Android. This affects an unknown code block of the component Setting Handler. The manipulation with an unknown input leads to a public cloneable() method without final ('object hijack') vulnerability. CWE is classifying the issue as CWE-491. A class has a cloneable() method that is not declared final, which allows an object to be created without calling the constructor. This can cause the object to be in an unexpected state. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Reolink v4.54.0.4.20250526 was discovered to contain a task hijacking vulnerability due to inappropriate taskAffinity settings.
The advisory is shared at relieved-knuckle-264.notion.site. This vulnerability is uniquely identified as CVE-2025-55622 since 08/13/2025. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
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
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Public cloneable() method without final ('object hijack')CWE: CWE-491
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
08/13/2025 CVE reserved08/22/2025 Advisory disclosed
08/22/2025 VulDB entry created
08/28/2025 VulDB entry last update
Sources
Advisory: relieved-knuckle-264.notion.siteStatus: Not defined
CVE: CVE-2025-55622 (🔒)
GCVE (CVE): GCVE-0-2025-55622
GCVE (VulDB): GCVE-100-321165
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 08/22/2025 23:57Updated: 08/28/2025 16:25
Changes: 08/22/2025 23:57 (54), 08/28/2025 16:25 (1)
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.