LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25101: 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_dmvpn function with the gre_key variable.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Milesight UR32L routers running v32.3.0.5 contain buffer overflows that can let a highly privileged attacker execute code through crafted HTTP requests. This is serious for organizations using these routers in operational or remote-network environments, but the source bundle does not show known active exploitation.

Executive priority

Treat this as a high-priority network device exposure if UR32L v32.3.0.5 is deployed. Business urgency is highest where router administration is broadly reachable or privileged accounts are weakly controlled.

Technical view

CVE-2023-25101 is a CWE-121 stack-based buffer overflow in the Milesight UR32L vtysh_ubus binary. The cited issue occurs in set_dmvpn through unsafe sprintf handling of the gre_key variable. CVSS 3.1 is 7.2, with network attack vector, low complexity, high privileges required, and high CIA impact.

Likely exposure

Exposure is limited to Milesight UR32L devices on firmware v32.3.0.5, especially where privileged HTTP access to management functions is reachable. The bundle does not identify other Milesight models or versions as affected.

Exploitation context

Sources state a specially crafted HTTP request can trigger arbitrary code execution, but the attacker needs high privileges. The CVE is not listed as KEV in the provided bundle, and no cited source in the bundle confirms exploitation in the wild.

Researcher notes

The key constraints are important: only UR32L v32.3.0.5 is named, high privileges are required, and no active exploitation is evidenced here. Remediation details are incomplete in the supplied bundle, so validation should focus on asset/version confirmation and access-path review.

Mitigation direction

  • Check Milesight guidance for fixed firmware or official remediation for UR32L v32.3.0.5.
  • Limit management HTTP access to trusted administrative networks and users.
  • Review privileged account access for UR32L management interfaces.
  • Monitor vendor and Talos advisories for update or mitigation details.

Validation and detection

  • Inventory Milesight UR32L devices and record firmware versions.
  • Flag any UR32L running v32.3.0.5 as potentially affected.
  • Verify whether HTTP management access is reachable beyond trusted administrators.
  • Check logs for unexpected privileged configuration activity where available.
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-25101 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-25101Attack 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.