LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25093: 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_qos function with the class_name variable..

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25093 is a high-severity memory corruption flaw in Milesight UR32L firmware v32.3.0.5. A highly privileged user who can send HTTP requests to the device may trigger a buffer overflow and potentially run code. Business risk is concentrated in organizations with this router model, exposed management interfaces, or weak admin account control.

Executive priority

Treat this as a targeted infrastructure risk, not a broad internet-wide emergency based on current evidence. Prioritize organizations using Milesight UR32L routers, especially where management access is reachable beyond tightly controlled admin networks.

Technical view

The flaw is a stack-based buffer overflow in the Milesight UR32L v32.3.0.5 vtysh_ubus binary. Talos attributes it to unsafe sprintf usage in set_qos handling of class_name. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Known exposure is limited to Milesight UR32L v32.3.0.5 based on the provided sources. Risk requires device presence, access to the HTTP management surface, and high-privilege credentials. The bundle provides no evidence that other Milesight models or firmware versions are affected.

Exploitation context

The sources describe exploitation through a specially crafted HTTP request by an attacker with high privileges. The CVE is not listed as CISA KEV in the bundle, and the provided sources do not report active exploitation or public weaponization.

Researcher notes

Evidence is strong for the affected product, vulnerable component, function, variable, CWE, and CVSS vector. Evidence is incomplete for patched versions, vendor workarounds, exploit availability, and impact on other firmware branches or models. Avoid broad claims without additional vendor confirmation.

Mitigation direction

  • Inventory Milesight UR32L deployments and confirm firmware versions.
  • Check Milesight guidance for a fixed firmware or vendor-approved workaround.
  • Restrict HTTP management access to trusted admin networks or VPN paths.
  • Review and reduce high-privilege accounts on affected devices.
  • Increase monitoring for unusual privileged management activity.

Validation and detection

  • Confirm whether any UR32L device runs firmware v32.3.0.5.
  • Verify management interfaces are not exposed to untrusted networks.
  • Review administrator accounts and remove unnecessary high-privilege access.
  • Check device and gateway logs for unexpected privileged HTTP management requests.
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-25093 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-25093Attack 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.