LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25092: 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 handle_interface_acl function with the interface and out_acl variables.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25092 affects Milesight UR32L routers running firmware v32.3.0.5. A highly privileged attacker can trigger a buffer overflow through a crafted HTTP request, potentially gaining arbitrary code execution. This is most urgent where affected devices are remotely managed or exposed beyond tightly controlled administrator networks.

Executive priority

Prioritize remediation for affected devices that manage sensitive networks or are reachable from broad internal or external networks. The high privilege requirement lowers immediate likelihood, but arbitrary code execution on network infrastructure can create serious operational and security impact.

Technical view

The flaw is a CWE-121 stack-based buffer overflow in the vtysh_ubus binary, caused by unsafe sprintf usage. The reported issue is in handle_interface_acl involving interface and out_acl variables. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, and high impact to confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to Milesight UR32L devices on v32.3.0.5. Risk depends heavily on who can reach the HTTP management surface and whether high-privilege credentials are available or compromised.

Exploitation context

The source says a specially crafted HTTP request can lead to arbitrary code execution, but requires high privileges. The bundle does not identify public exploitation, and KEV status is false. Treat exploitation as plausible post-authentication risk, not confirmed active exploitation.

Researcher notes

Available evidence identifies the vulnerable binary, function, variables, affected firmware, and attack precondition. The bundle does not include a named fixed version, vendor workaround, or confirmed exploitation. Avoid assuming other Milesight products or firmware versions are affected without vendor confirmation.

Mitigation direction

  • Check Milesight guidance for fixed firmware or vendor-approved workarounds.
  • Upgrade or replace affected UR32L v32.3.0.5 devices per vendor guidance.
  • Restrict administrative HTTP access to trusted management networks.
  • Remove unnecessary high-privilege accounts and review administrator credential hygiene.
  • Monitor vendor, CVE, and Talos references for remediation updates.

Validation and detection

  • Inventory Milesight UR32L devices and record firmware versions.
  • Confirm whether any device is running v32.3.0.5.
  • Review management-plane exposure for affected devices.
  • Check logs for unusual privileged HTTP administration activity.
  • Recheck CVE and vendor references for updated remediation details.
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-25092 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-25092Attack 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.