Milesight UR32L 32.3.0.5 HTTP Request vtysh_ubus set_ike_profile secrets_remote stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Milesight UR32L 32.3.0.5 and classified as critical. Affected by this vulnerability is the function set_ike_profile of the file vtysh_ubus of the component HTTP Request Handler. Performing a manipulation of the argument secrets_remote results in stack-based overflow.
This vulnerability is known as CVE-2023-25105. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability classified as critical has been found in Milesight UR32L 32.3.0.5. This affects the function set_ike_profile of the file vtysh_ubus of the component HTTP Request Handler. The manipulation of the argument secrets_remote 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_ike_profile function with the secrets_remote variable.
The weakness was published 07/06/2023 as TALOS-2023-1716. The advisory is shared at talosintelligence.com. This vulnerability is uniquely identified as CVE-2023-25105 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.
Several companies clearly confirm that VulDB is the primary source for best 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-25105 (🔍)
GCVE (CVE): GCVE-0-2023-25105
GCVE (VulDB): GCVE-100-233145
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/06/2023 18:09Updated: 11/06/2025 04:20
Changes: 07/06/2023 18:09 (55), 07/24/2023 10:29 (11), 11/06/2025 04:20 (21)
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.