LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25117: Multiple buffer overflow vulnerabilities exist in the vtysh_ubus binary of Milesight UR32L v32.3.0.5 due to...

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 local_virtual_ip and the local_virtual_mask variables.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25117 affects Milesight UR32L routers running v32.3.0.5. A privileged attacker can send a crafted HTTP request that triggers a buffer overflow and may execute arbitrary code. Business risk is highest where these devices are used for remote connectivity, VPN, or site networking and their management interface is reachable.

Executive priority

Treat this as a high-priority network-edge device issue, especially for remote sites or VPN-dependent operations. The privilege requirement lowers opportunistic risk, but compromise could affect routing, confidentiality, and availability. Prioritize exposure reduction while checking vendor remediation guidance.

Technical view

Talos reports unsafe sprintf use in the vtysh_ubus binary. The overflow is in set_openvpn_client, involving local_virtual_ip and local_virtual_mask handling. The CVSS 3.1 score is 7.2, reflecting network access, low attack complexity, high privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Known affected exposure is limited to Milesight UR32L firmware v32.3.0.5 in the provided sources. Environments should prioritize internet-reachable or broadly reachable HTTP management interfaces, shared administrative accounts, and devices used for VPN or operational network routing.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires high privileges and a crafted HTTP request. The impact is still serious because successful exploitation can lead to arbitrary code execution on a network edge device.

Researcher notes

Evidence is specific to vtysh_ubus on Milesight UR32L v32.3.0.5. The described vulnerable fields are local_virtual_ip and local_virtual_mask in set_openvpn_client. The bundle does not identify patched versions, exploit-in-the-wild evidence, or broader affected firmware families.

Mitigation direction

  • Inventory Milesight UR32L devices and identify firmware v32.3.0.5.
  • Check Milesight guidance for fixed firmware or vendor-recommended mitigations.
  • Restrict HTTP management access to trusted administration networks only.
  • Review and reduce high-privilege accounts with access to affected devices.
  • Monitor device logs for unusual administrative changes or OpenVPN configuration activity.

Validation and detection

  • Confirm device model and firmware version from authorized management channels.
  • Verify whether management interfaces are reachable from untrusted networks.
  • Review administrative account membership and recent privileged login history.
  • Check OpenVPN client configuration changes for unexpected values or timing.
  • Track remediation status against vendor guidance and internal asset inventory.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-25117 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2023-25117Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MilesightUR32Lv32.3.0.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.