Totolink EX200 4.0.3c.7646_B20201211 setUpgradeFW FileName special elements into a different plane (special element injection)
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Totolink EX200 4.0.3c.7646_B20201211. Affected is the function setUpgradeFW. This manipulation of the argument FileName causes Remote Privilege Escalation.
This vulnerability appears as CVE-2024-31809. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability has been found in Totolink EX200 4.0.3c.7646_B20201211 and classified as critical. Affected by this vulnerability is the function setUpgradeFW. The manipulation of the argument FileName with an unknown input leads to a remote privilege escalation vulnerability. The CWE definition for the vulnerability is CWE-75. The product does not adequately filter user-controlled input for special elements with control implications. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
TOTOLINK EX200 V4.0.3c.7646_B20201211 was discovered to contain a remote code execution (RCE) vulnerability via the FileName parameter in the setUpgradeFW function.
The advisory is shared at github.com. This vulnerability is known as CVE-2024-31809 since 04/05/2024. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.totolink.net/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: Failure to sanitize special elements into a different plane (special element injection)CWE: CWE-75 / CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
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
04/05/2024 🔍04/08/2024 🔍
04/08/2024 🔍
03/18/2025 🔍
Sources
Vendor: totolink.netAdvisory: github.com
Status: Not defined
CVE: CVE-2024-31809 (🔍)
GCVE (CVE): GCVE-0-2024-31809
GCVE (VulDB): GCVE-100-259753
Entry
Created: 04/08/2024 14:52Updated: 03/18/2025 17:15
Changes: 04/08/2024 14:52 (51), 03/18/2025 17:15 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.