LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25081: 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 firewall_handler_set function with the src and dmz variables.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects Milesight UR32L routers running firmware v32.3.0.5. A highly privileged attacker can send a crafted HTTP request that may execute code on the device. The business risk is concentrated in environments where these routers manage remote connectivity or critical network segments.

Executive priority

Treat this as high priority where UR32L devices support business-critical connectivity. The privilege requirement lowers broad external risk, but successful exploitation could give an attacker full device control and disrupt network availability or integrity.

Technical view

CVE-2023-25081 is a CWE-121 stack buffer overflow in the Milesight UR32L vtysh_ubus binary. The issue is tied to unsafe sprintf use in firewall_handler_set involving src and dmz variables. CVSS 3.1 is 7.2, with network attack vector, low complexity, high privileges, no user interaction, and high CIA impact.

Likely exposure

Exposure appears limited to Milesight UR32L devices on v32.3.0.5. Risk increases if the HTTP management interface is reachable beyond tightly controlled administrator networks or if privileged device credentials are compromised.

Exploitation context

The supplied sources describe arbitrary code execution via a specially crafted HTTP request by an attacker with high privileges. CISA KEV is false, and the bundle provides no evidence of active exploitation in the wild.

Researcher notes

Evidence is specific to vtysh_ubus and firewall_handler_set handling of src and dmz variables. The supplied bundle does not name a patched version, public exploit, or active campaign. Avoid assuming broader Milesight product impact without additional vendor evidence.

Mitigation direction

  • Inventory Milesight UR32L deployments and confirm firmware versions.
  • Restrict HTTP management access to trusted admin networks or VPN only.
  • Review and reduce privileged accounts on affected devices.
  • Check Milesight and Talos guidance for fixed firmware or official mitigations.
  • Monitor device logs for unusual privileged firewall or DMZ configuration activity.

Validation and detection

  • Confirm whether any UR32L devices run firmware v32.3.0.5.
  • Verify the management interface is not exposed to untrusted networks.
  • Review access logs for unexpected privileged HTTP configuration changes.
  • Confirm vendor guidance has been reviewed before declaring remediation complete.
  • Document compensating controls if no vendor fix is available.
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-25081 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-25081Attack 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.