Elink Smart eSmartCam App 2.1.5 on Android hard-coded key
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Elink Smart eSmartCam App 2.1.5 on Android. Affected by this vulnerability is an unknown functionality. The manipulation leads to hard-coded key. This vulnerability is known as CVE-2024-25731. The attack can be launched remotely. There is no exploit available. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Details
A vulnerability classified as problematic has been found in Elink Smart eSmartCam App 2.1.5 on Android (Android App Software). Affected is some unknown functionality. The manipulation with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality. CVE summarizes:
The Elink Smart eSmartCam (com.cn.dq.ipc) application 2.1.5 for Android contains hardcoded AES encryption keys that can be extracted from a binary file. Thus, encryption can be defeated by an attacker who can observe packet data (e.g., over Wi-Fi).
The weakness was released 03/05/2024. The advisory is available at github.com. This vulnerability is traded as CVE-2024-25731 since 02/11/2024. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
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
02/11/2024 🔍03/05/2024 🔍
03/05/2024 🔍
02/26/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-25731 (🔍)
GCVE (CVE): GCVE-0-2024-25731
GCVE (VulDB): GCVE-100-255726
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 03/05/2024 08:45 AMUpdated: 02/26/2025 07:58 PM
Changes: 03/05/2024 08:45 AM (38), 02/26/2025 07:58 PM (27)
Complete: 🔍
Cache ID: 18:CC9:40
No comments yet. Languages: en.
Please log in to comment.