LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25116: 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 remote_virtual_ip variables.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25116 affects Milesight UR32L firmware v32.3.0.5. A privileged attacker can send a crafted HTTP request that may crash or take control of the device. Business urgency is highest where these routers support remote sites, industrial connectivity, or exposed management interfaces.

Executive priority

Treat as high priority for environments using Milesight UR32L v32.3.0.5. The privilege requirement lowers broad internet risk, but successful exploitation could provide full device compromise affecting connectivity and site operations.

Technical view

The issue is a stack buffer overflow, CWE-121, in the Milesight UR32L vtysh_ubus binary. Talos attributes it to unsafe sprintf usage in set_openvpn_client involving local_virtual_ip and remote_virtual_ip. The CVSS 3.1 score is 7.2 with network attack vector and high privileges required.

Likely exposure

Known exposure is limited in the provided sources to Milesight UR32L devices running v32.3.0.5. Systems with reachable administrative HTTP access, weak privileged-account control, or remote management paths deserve priority review.

Exploitation context

The sources state exploitation requires high privileges and a specially crafted HTTP request. CISA KEV status is false in the bundle, and no provided source confirms active exploitation. Public Talos reporting means defenders should assume technical details are available.

Researcher notes

Evidence identifies the vulnerable binary, function, variables, CWE, CVSS vector, and affected firmware. The provided bundle does not name a fixed version, workaround, proof of exploitation, or broader affected product set.

Mitigation direction

  • Identify all Milesight UR32L devices and firmware versions.
  • Check Milesight guidance for a fixed firmware or vendor-recommended workaround.
  • Restrict administrative HTTP access to trusted management networks.
  • Review and limit high-privilege accounts on affected devices.
  • Increase monitoring around remote management access and configuration changes.

Validation and detection

  • Confirm whether any UR32L devices run firmware v32.3.0.5.
  • Verify administrative HTTP interfaces are not exposed to untrusted networks.
  • Review privileged login and configuration-change logs for unusual activity.
  • Track CVE, Talos, and Milesight advisories for remediation details.
Prepared
Confidence
high
Sources
3

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-25116 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-25116Attack 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.