LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25100: 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 default_class variable.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects Milesight UR32L industrial routers running firmware v32.3.0.5. A privileged attacker can send a crafted HTTP request that triggers a buffer overflow and may execute code on the device. Business risk is highest where these routers are reachable beyond trusted administration networks.

Executive priority

Treat this as a high-priority infrastructure exposure if affected routers support operations, remote sites, or sensitive networks. Prioritize network restriction and vendor remediation because successful exploitation could compromise the router itself.

Technical view

CVE-2023-25100 is a CWE-121 buffer overflow in the vtysh_ubus binary. The issue is tied to unsafe sprintf usage in set_qos handling of the default_class variable. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Milesight UR32L devices on firmware v32.3.0.5, especially where the HTTP management surface is reachable by privileged users outside a tightly controlled admin network.

Exploitation context

The sources describe arbitrary code execution through a crafted HTTP request by an attacker with high privileges. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation.

Researcher notes

Evidence identifies the affected binary, function, variable, firmware version, privilege requirement, and impact. The bundle does not provide a confirmed patch version or exploitation-in-the-wild evidence, so remediation should be anchored to current Milesight guidance.

Mitigation direction

  • Inventory Milesight UR32L devices and identify firmware v32.3.0.5.
  • Restrict HTTP management access to trusted admin networks or VPN paths.
  • Review Milesight support guidance for fixed firmware or official remediation.
  • Minimize and audit high-privileged device accounts.
  • Monitor for unusual privileged configuration changes on affected routers.

Validation and detection

  • Confirm device model and firmware version from inventory or the admin interface.
  • Check whether HTTP management is reachable from untrusted networks.
  • Review access logs for unexpected privileged administration activity.
  • Track remediation status against Milesight or Talos advisory guidance.
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-25100 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-25100Attack 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.