LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25113: 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_l2tp function with the key variable.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Milesight UR32L firmware v32.3.0.5 has a high-severity memory corruption flaw. A privileged attacker who can reach the HTTP management surface could trigger a buffer overflow and potentially run code on the device. This matters most where these routers support operational networks or remote sites.

Executive priority

Prioritize affected devices in operational or remote connectivity roles. The flaw is high impact but requires privileged access, so urgency depends on management-interface exposure and admin-account control. Treat internet-reachable or broadly reachable management planes as a faster remediation priority.

Technical view

CVE-2023-25113 is a CWE-121 stack buffer overflow in the vtysh_ubus binary. The issue is tied to unsafe sprintf usage in set_l2tp involving the key variable. Talos reports that a specially crafted HTTP request can cause arbitrary code execution, but the CVSS vector requires high privileges.

Likely exposure

Exposure is limited to Milesight UR32L devices running v32.3.0.5. Risk increases when HTTP administration is reachable from broad internal networks, remote access paths, or shared privileged accounts. The provided sources do not identify other affected products or versions.

Exploitation context

The cited record says exploitation requires high privileges and network access, with no user interaction. The bundle does not show CISA KEV listing or confirmed active exploitation. Public evidence here supports potential arbitrary code execution, not observed exploitation in the wild.

Researcher notes

Focus validation on the vtysh_ubus set_l2tp path and the key variable described by Talos. Avoid assuming unauthenticated reachability: the CVSS vector is PR:H. The source bundle does not provide a named fixed version, workaround, or active-exploitation evidence.

Mitigation direction

  • Identify Milesight UR32L devices and confirm firmware versions.
  • Check Milesight or Talos guidance for fixed firmware or official mitigations.
  • Restrict HTTP management access to trusted administrative networks or VPNs.
  • Limit and review high-privilege administrative accounts on affected devices.
  • Monitor device administration logs for unusual L2TP or configuration activity.

Validation and detection

  • Verify whether any UR32L device runs firmware v32.3.0.5.
  • Confirm HTTP management interfaces are not internet-exposed.
  • Review who has high-privilege access to affected devices.
  • Check recent administrative activity for unexpected configuration changes.
  • Document compensating controls until vendor remediation is confirmed.
Prepared
Confidence
high
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-25113 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-25113Attack 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.