CVE-2023-25115: CWE-121: Stack-based Buffer Overflow in Milesight UR32L
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_openvpn_client function with the remote_ip and the port variables.
AI Analysis
Technical Summary
CVE-2023-25115 is a stack-based buffer overflow vulnerability identified in the vtysh_ubus binary of the Milesight UR32L router, specifically in version 32.3.0.5. The root cause is the unsafe use of the sprintf function within the set_openvpn_client function, which processes the remote_ip and port parameters from HTTP requests. Because sprintf does not perform bounds checking, specially crafted inputs can overflow the stack buffer, corrupting memory and enabling arbitrary code execution. Exploitation requires the attacker to have high privileges, meaning they must already have authenticated access or elevated rights on the device. The vulnerability affects confidentiality, integrity, and availability, as arbitrary code execution can lead to data leakage, device manipulation, or denial of service. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no user interaction (UI:N), and unchanged scope (S:U). The CVSS v3.1 base score is 7.2, reflecting a high severity. Although no public exploits have been reported, the critical nature of the vulnerability and the device’s role in network infrastructure make it a significant risk. The lack of available patches at the time of reporting necessitates immediate mitigation steps to reduce exposure.
Potential Impact
For European organizations, the impact of this vulnerability can be substantial, especially for those relying on Milesight UR32L devices for network routing, VPN connectivity, or other critical infrastructure roles. Successful exploitation could allow attackers to execute arbitrary code, potentially leading to full device compromise, interception or manipulation of network traffic, disruption of VPN services, and lateral movement within internal networks. This could result in data breaches, operational downtime, and loss of trust. Given the high privileges required for exploitation, insider threats or attackers who have already gained initial access pose the greatest risk. The vulnerability’s network exposure means that devices accessible from less trusted network segments or the internet are particularly vulnerable. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits in the future. Organizations in sectors such as telecommunications, critical infrastructure, and enterprises with distributed networks are especially at risk.
Mitigation Recommendations
1. Immediately restrict access to the management interfaces of Milesight UR32L devices, ensuring only trusted and authenticated users can reach the HTTP service. 2. Implement network segmentation to isolate these devices from untrusted networks and reduce attack surface exposure. 3. Monitor network traffic for unusual or malformed HTTP requests targeting the vtysh_ubus service, using IDS/IPS solutions with custom signatures if possible. 4. Enforce strict authentication and authorization policies to prevent unauthorized privilege escalation. 5. Regularly audit device configurations and logs for signs of exploitation attempts or anomalous behavior. 6. Engage with the vendor for patches or firmware updates addressing this vulnerability and apply them promptly once available. 7. Consider deploying compensating controls such as application-layer firewalls or reverse proxies to filter malicious requests. 8. Educate network administrators about the vulnerability and the importance of limiting high-privilege access.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Belgium, Sweden, Austria
CVE-2023-25115: CWE-121: Stack-based Buffer Overflow in Milesight UR32L
Description
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_openvpn_client function with the remote_ip and the port variables.
AI-Powered Analysis
Technical Analysis
CVE-2023-25115 is a stack-based buffer overflow vulnerability identified in the vtysh_ubus binary of the Milesight UR32L router, specifically in version 32.3.0.5. The root cause is the unsafe use of the sprintf function within the set_openvpn_client function, which processes the remote_ip and port parameters from HTTP requests. Because sprintf does not perform bounds checking, specially crafted inputs can overflow the stack buffer, corrupting memory and enabling arbitrary code execution. Exploitation requires the attacker to have high privileges, meaning they must already have authenticated access or elevated rights on the device. The vulnerability affects confidentiality, integrity, and availability, as arbitrary code execution can lead to data leakage, device manipulation, or denial of service. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no user interaction (UI:N), and unchanged scope (S:U). The CVSS v3.1 base score is 7.2, reflecting a high severity. Although no public exploits have been reported, the critical nature of the vulnerability and the device’s role in network infrastructure make it a significant risk. The lack of available patches at the time of reporting necessitates immediate mitigation steps to reduce exposure.
Potential Impact
For European organizations, the impact of this vulnerability can be substantial, especially for those relying on Milesight UR32L devices for network routing, VPN connectivity, or other critical infrastructure roles. Successful exploitation could allow attackers to execute arbitrary code, potentially leading to full device compromise, interception or manipulation of network traffic, disruption of VPN services, and lateral movement within internal networks. This could result in data breaches, operational downtime, and loss of trust. Given the high privileges required for exploitation, insider threats or attackers who have already gained initial access pose the greatest risk. The vulnerability’s network exposure means that devices accessible from less trusted network segments or the internet are particularly vulnerable. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits in the future. Organizations in sectors such as telecommunications, critical infrastructure, and enterprises with distributed networks are especially at risk.
Mitigation Recommendations
1. Immediately restrict access to the management interfaces of Milesight UR32L devices, ensuring only trusted and authenticated users can reach the HTTP service. 2. Implement network segmentation to isolate these devices from untrusted networks and reduce attack surface exposure. 3. Monitor network traffic for unusual or malformed HTTP requests targeting the vtysh_ubus service, using IDS/IPS solutions with custom signatures if possible. 4. Enforce strict authentication and authorization policies to prevent unauthorized privilege escalation. 5. Regularly audit device configurations and logs for signs of exploitation attempts or anomalous behavior. 6. Engage with the vendor for patches or firmware updates addressing this vulnerability and apply them promptly once available. 7. Consider deploying compensating controls such as application-layer firewalls or reverse proxies to filter malicious requests. 8. Educate network administrators about the vulnerability and the importance of limiting high-privilege access.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- talos
- Date Reserved
- 2023-02-02T20:42:36.075Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 690a531b2a90255b94da5eb3
Added to database: 11/4/2025, 7:25:15 PM
Last enriched: 11/4/2025, 8:59:54 PM
Last updated: 11/6/2025, 1:38:38 PM
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2024-5651: Improper Control of Generation of Code ('Code Injection')
HighCVE-2024-57520: n/a
CriticalCVE-2025-11268: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wpchill Strong Testimonials
MediumCVE-2025-12360: CWE-285 Improper Authorization in codesolz Better Find and Replace – AI-Powered Suggestions
MediumCVE-2025-10259: CWE-1284 Improper Validation of Specified Quantity in Input in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5U-32MT/ES
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.