Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2023-25081: CWE-121: Stack-based Buffer Overflow in Milesight UR32L

0
High
VulnerabilityCVE-2023-25081cvecve-2023-25081cwe-121
Published: Thu Jul 06 2023 (07/06/2023, 14:53:23 UTC)
Source: CVE Database V5
Vendor/Project: Milesight
Product: 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 firewall_handler_set function with the src and dmz variables.

AI-Powered Analysis

AILast updated: 11/04/2025, 21:17:16 UTC

Technical Analysis

CVE-2023-25081 is a stack-based buffer overflow vulnerability identified in the vtysh_ubus binary of the Milesight UR32L router firmware version 32.3.0.5. The root cause is the unsafe use of the sprintf function within the firewall_handler_set function, specifically when handling the src and dmz variables. This unsafe pattern allows an attacker with high privileges to craft malicious HTTP requests that overflow the stack buffer, leading to arbitrary code execution on the device. The vulnerability is categorized under CWE-121, which pertains to stack-based buffer overflows, a common and dangerous class of memory corruption bugs. The CVSS v3.1 base score is 7.2, indicating high severity, with attack vector as network (remote), low attack complexity, requiring high privileges but no user interaction, and impacting confidentiality, integrity, and availability. The vulnerability could allow attackers to fully compromise the device, potentially pivoting into internal networks or disrupting network operations. No patches or known exploits have been reported as of the publication date. The vulnerability affects a specific firmware version, so devices running v32.3.0.5 are at risk. The lack of patches necessitates immediate risk mitigation through network segmentation, access controls, and monitoring.

Potential Impact

For European organizations, this vulnerability poses a significant risk, especially for those deploying Milesight UR32L routers in enterprise, industrial, or critical infrastructure environments. Successful exploitation could lead to full device compromise, allowing attackers to intercept, modify, or disrupt network traffic, potentially causing data breaches, service outages, or lateral movement within networks. Given the device's role as a router/firewall, the impact on confidentiality, integrity, and availability is severe. Disruption or compromise of network perimeter devices can have cascading effects on organizational security posture. The requirement for high privileges limits exposure somewhat, but insider threats or compromised administrative credentials could enable exploitation. The absence of patches increases the window of vulnerability, making proactive mitigation critical. European organizations with regulatory obligations around data protection and network security may face compliance risks if this vulnerability is exploited.

Mitigation Recommendations

1. Immediately audit and restrict administrative access to the Milesight UR32L devices to trusted personnel only, enforcing strong authentication mechanisms such as multifactor authentication. 2. Implement network segmentation to isolate vulnerable devices from critical network segments, limiting potential lateral movement if compromised. 3. Employ strict firewall rules and access control lists to restrict HTTP access to the device management interface to trusted IP addresses only. 4. Monitor network traffic and device logs for unusual HTTP requests or signs of exploitation attempts targeting the vtysh_ubus service. 5. Coordinate with Milesight support or vendor channels to obtain firmware updates or patches as soon as they become available. 6. Consider deploying intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics to detect exploitation attempts. 7. If possible, temporarily disable or restrict the vulnerable service or interface until a patch is applied. 8. Maintain an incident response plan specific to network device compromise scenarios to rapidly contain and remediate any incidents.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
talos
Date Reserved
2023-02-02T20:42:36.068Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690a53152a90255b94da5793

Added to database: 11/4/2025, 7:25:09 PM

Last enriched: 11/4/2025, 9:17:16 PM

Last updated: 11/6/2025, 1:51:24 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats