LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25095: 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 rule_name variable with two possible format strings that represent negated commands.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue affects Milesight UR32L routers running firmware v32.3.0.5. A high-privileged attacker who can send HTTP requests to the device may trigger a memory corruption flaw and potentially run code on the router. Business urgency is highest where these devices manage sensitive networks or remote sites.

Executive priority

Treat as a high-priority infrastructure risk for any deployed UR32L v32.3.0.5 device. The privilege requirement reduces broad internet-scale risk, but routers often sit at sensitive network boundaries where code execution can create operational and security impact.

Technical view

CVE-2023-25095 is a CWE-121 stack-based buffer overflow in the Milesight UR32L vtysh_ubus binary. The reported flaw is in set_qos handling of rule_name, caused by unsafe sprintf usage with negated command format strings. CVSS 3.1 is 7.2: network-reachable, low complexity, high privileges required, no user interaction.

Likely exposure

Exposure is limited to Milesight UR32L devices on firmware v32.3.0.5, especially where the HTTP management path is reachable by privileged users. The source bundle does not identify other Milesight models, firmware versions, or CPEs as affected.

Exploitation context

The supplied sources do not show KEV listing or cited active exploitation. The vulnerability requires high privileges, but successful exploitation could provide arbitrary code execution with high confidentiality, integrity, and availability impact.

Researcher notes

Evidence is specific but narrow: affected product, version, function, variable, weakness class, and CVSS are provided. The bundle does not provide an official patch version, exploitation-in-the-wild evidence, or broadened affected-version range, so avoid extrapolating beyond UR32L v32.3.0.5.

Mitigation direction

  • Inventory Milesight UR32L devices and identify firmware v32.3.0.5.
  • Check Milesight guidance or support channels for fixed firmware or official mitigations.
  • Restrict HTTP management access to trusted administrative networks or VPN paths.
  • Review and minimize high-privilege accounts on affected devices.
  • Prioritize replacement or isolation if no vendor fix is available.

Validation and detection

  • Confirm device model and firmware version from asset records or management UI.
  • Verify whether HTTP management is reachable from untrusted networks.
  • Review administrative account lists for unnecessary high-privilege users.
  • Check vendor advisories against the exact firmware version deployed.
  • Monitor device logs for unexpected privileged configuration activity.
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-25095 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-25095Attack 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.