Milesight UR32L 32.3.0.5 HTTP Request vtysh_ubus set_l2tp key stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Milesight UR32L 32.3.0.5. Affected is the function set_l2tp of the file vtysh_ubus of the component HTTP Request Handler. Performing a manipulation of the argument key results in stack-based overflow.
This vulnerability is cataloged as CVE-2023-25113. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Details
A vulnerability classified as critical has been found in Milesight UR32L 32.3.0.5. This affects the function set_l2tp of the file vtysh_ubus of the component HTTP Request Handler. The manipulation of the argument key with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Multiple buffer overflow vulnerabilities exist in the vtysh_ubus binary of Milesight UR32L v32.3.0.5 due to the use of an unsafe sprintf pattern. A specially crafted HTTP request can lead to arbitrary code execution. An attacker with high privileges can send HTTP requests to trigger these vulnerabilities.This buffer overflow occurs in the set_l2tp function with the key variable.
The weakness was shared 07/06/2023 as TALOS-2023-1716. It is possible to read the advisory at talosintelligence.com. This vulnerability is uniquely identified as CVE-2023-25113 since 02/02/2023. Technical details and a public exploit are known.
The exploit is shared for download at talosintelligence.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.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.2
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
CNA Base Score: 7.2
CNA Vector (Talos): 🔍
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: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/02/2023 🔍07/06/2023 🔍
07/06/2023 🔍
11/06/2025 🔍
Sources
Advisory: TALOS-2023-1716Status: Not defined
CVE: CVE-2023-25113 (🔍)
GCVE (CVE): GCVE-0-2023-25113
GCVE (VulDB): GCVE-100-233199
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/06/2023 18:32Updated: 11/06/2025 04:20
Changes: 07/06/2023 18:32 (55), 07/24/2023 14:27 (11), 11/06/2025 04:20 (21)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.