LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25089: 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 in_acl is -1.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25089 is a high-severity flaw in Milesight UR32L firmware v32.3.0.5. An authenticated, high-privilege attacker could send crafted HTTP requests that trigger a buffer overflow and may gain arbitrary code execution on the device.

Executive priority

Prioritize remediation for exposed or operationally critical UR32L routers. The high-privilege requirement lowers broad opportunistic risk, but successful compromise could provide full confidentiality, integrity, and availability impact on affected network equipment.

Technical view

Talos reports multiple stack buffer overflows in the vtysh_ubus binary caused by unsafe sprintf use. This instance affects handle_interface_acl when processing the interface variable with in_acl set to -1. The CVSS 3.1 score is 7.2, with network access, low complexity, and high privileges required.

Likely exposure

Exposure is limited to organizations using Milesight UR32L devices running firmware v32.3.0.5. Risk increases if the web management interface is reachable from broad internal networks or the internet, but exploitation requires high privileges according to the CVE data.

Exploitation context

The provided sources describe a crafted HTTP request path to arbitrary code execution, but do not cite active exploitation. The CVE is not listed as KEV in the supplied bundle, so treat exploitation as possible but not confirmed.

Researcher notes

Evidence is centered on Talos and CVE records. The vulnerable component is vtysh_ubus, with a stack overflow classified as CWE-121. The supplied sources do not name a patch version, workaround, or confirmed exploitation campaign.

Mitigation direction

  • Inventory Milesight UR32L devices and identify firmware v32.3.0.5.
  • Restrict HTTP administration to trusted management networks or VPN.
  • Remove internet exposure for UR32L management interfaces.
  • Enforce least-privilege administrative access and strong authentication controls.
  • Check Milesight guidance for fixed firmware or supported mitigations.

Validation and detection

  • Confirm whether any UR32L device runs firmware v32.3.0.5.
  • Verify management HTTP access is not publicly reachable.
  • Review administrative access lists for unnecessary high-privilege accounts.
  • Check logs for unusual authenticated management activity.
  • Track CVE, Talos, and vendor references for remediation updates.
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-25089 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-25089Attack 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.