LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25091: 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 variable when out_acl is -1.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25091 is a high-impact flaw in Milesight UR32L firmware v32.3.0.5. A highly privileged attacker can send a crafted HTTP request that may cause arbitrary code execution on the device. The main business concern is loss of control over exposed router management functions, especially in remote or operational environments.

Executive priority

Treat this as a high-priority remediation item for any affected UR32L device that supports business connectivity or remote operations. The privilege requirement lowers broad internet-scale risk, but successful exploitation could fully compromise device confidentiality, integrity, and availability.

Technical view

Talos describes multiple stack-based buffer overflows in the UR32L vtysh_ubus binary caused by unsafe sprintf use. This CVE maps to handle_interface_acl, involving the interface variable when out_acl is -1. CVSS 3.1 is 7.2, with network attack vector, low complexity, high privileges required, no user interaction, and high CIA impact.

Likely exposure

Exposure appears limited to Milesight UR32L devices running firmware v32.3.0.5. Risk increases when the HTTP management interface is reachable beyond trusted administration networks or when high-privilege credentials are shared, weak, or compromised.

Exploitation context

The source bundle supports arbitrary code execution via crafted HTTP requests by an attacker with high privileges. It does not show CISA KEV listing or confirmed active exploitation. Public exploit status is not established by the provided evidence.

Researcher notes

Key evidence is narrow but useful: affected product UR32L v32.3.0.5, vtysh_ubus, CWE-121, unsafe sprintf, handle_interface_acl, interface variable, out_acl equals -1. No vendor patch details are included in the supplied bundle, so remediation should be tied to vendor guidance.

Mitigation direction

  • Inventory Milesight UR32L devices and identify firmware v32.3.0.5.
  • Check Milesight and Talos guidance for fixed firmware or vendor mitigations.
  • Restrict HTTP management access to trusted admin networks or VPN only.
  • Review and reduce high-privilege administrative accounts on affected devices.
  • Monitor device management logs for unusual interface ACL changes.

Validation and detection

  • Confirm each UR32L device firmware version from trusted asset records or admin UI.
  • Verify management interfaces are not exposed to untrusted networks.
  • Audit high-privilege device accounts and recent authentication activity.
  • Review logs for unexpected HTTP administration activity around interface ACL settings.
  • Track remediation status against the Talos advisory and CVE record.
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-25091 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-25091Attack 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.