Shenzhen Libituo Technology LBT-T300-T400 3.2 rc tftp_image_check default permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Shenzhen Libituo Technology LBT-T300-T400 3.2. This vulnerability affects the function tftp_image_check of the file rc. The manipulation results in an unknown weakness.
This vulnerability is identified as CVE-2025-29570. The attack is only possible with local access. There is not any exploit available.
Details
A vulnerability was found in Shenzhen Libituo Technology LBT-T300-T400 3.2. It has been classified as problematic. Affected is the function tftp_image_check of the file rc. CWE is classifying the issue as CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. The impact remains unknown. CVE summarizes:
An issue in Shenzhen Libituo Technology Co., Ltd LBT-T300-T400 v3.2 allows a local attacker to escalate privileges via the function tftp_image_check of a binary named rc.
The advisory is available at github.com. This vulnerability is traded as CVE-2025-29570 since 03/11/2025. The exploitability is told to be easy. Local access is required to approach this attack. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1222 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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Default permissionCWE: CWE-276 / 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
03/11/2025 🔍04/04/2025 🔍
04/04/2025 🔍
08/20/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2025-29570 (🔍)
GCVE (CVE): GCVE-0-2025-29570
GCVE (VulDB): GCVE-100-303306
Entry
Created: 04/04/2025 07:21Updated: 08/20/2025 04:58
Changes: 04/04/2025 07:21 (52), 08/20/2025 04:58 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.