LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25112: 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 remote_subnet and the remote_mask variables.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25112 affects Milesight UR32L routers running v32.3.0.5. A highly privileged attacker can send a crafted HTTP request that may cause arbitrary code execution. Business urgency is highest where these routers support critical connectivity or exposed management access.

Executive priority

Treat this as high priority for any UR32L v32.3.0.5 device in production. High privileges are required, but successful exploitation could compromise router confidentiality, integrity, and availability, making exposure of management access the key business risk.

Technical view

The issue is a CWE-121 stack buffer overflow in the vtysh_ubus binary. Talos describes unsafe sprintf usage in set_l2tp involving remote_subnet and remote_mask variables. CVSS 3.1 is 7.2, with network attack vector, low complexity, high privileges required, no user interaction, and high CIA impact.

Likely exposure

Organizations using Milesight UR32L v32.3.0.5 are in scope, especially where administrative HTTP access is reachable over management networks or remote access paths. The supplied sources name only UR32L v32.3.0.5; do not assume other models or versions without vendor confirmation.

Exploitation context

The sources describe exploitation by a specially crafted HTTP request from an attacker with high privileges. The CVE is not listed as KEV in the supplied data, and no cited source here confirms active exploitation in the wild.

Researcher notes

The supplied evidence supports a stack buffer overflow in vtysh_ubus set_l2tp handling. Patch status and broader version impact are not established in the bundle. Validate exposure defensively without reproducing crafted requests against production devices.

Mitigation direction

  • Inventory Milesight UR32L devices and identify firmware versions.
  • Check Milesight or Talos guidance for fixed firmware or vendor workarounds.
  • Restrict administrative HTTP access to trusted management networks only.
  • Review high-privilege router accounts and remove unnecessary access.
  • Monitor for unusual L2TP configuration changes or admin activity.

Validation and detection

  • Confirm whether any UR32L device runs v32.3.0.5.
  • Verify administrative HTTP interfaces are not internet-accessible.
  • Review device logs for unexpected privileged HTTP administration activity.
  • Check L2TP configuration history for unusual remote_subnet or remote_mask changes.
  • Document compensating controls if no vendor fix is deployed.
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-25112 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-25112Attack 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.