LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25109: 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_gre function with the local_ip variable.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Milesight UR32L firmware v32.3.0.5 has a buffer overflow in a management-related binary. A highly privileged attacker can trigger it through HTTP and potentially run code on the device. The business risk is highest where these routers are reachable by many administrators or exposed management networks.

Executive priority

Treat this as a high-priority network device issue when UR32L v32.3.0.5 is deployed. It requires high privileges, so urgency is lower than unauthenticated remote code execution, but compromise could affect routing, availability, and trust in edge infrastructure.

Technical view

CVE-2023-25109 is a CWE-121 stack buffer overflow in Milesight UR32L v32.3.0.5 vtysh_ubus. Talos attributes it to unsafe sprintf use in set_gre handling of local_ip. CVSS 3.1 is 7.2, with network attack vector, low complexity, high privileges, no user interaction, and high CIA impact.

Likely exposure

Confirmed affected scope in the bundle is Milesight UR32L running firmware v32.3.0.5. Exposure depends on whether authenticated, high-privilege users can reach the device HTTP management surface. Do not assume other Milesight products or firmware versions are affected from this evidence alone.

Exploitation context

The bundle supports arbitrary code execution via specially crafted HTTP requests, but only by an attacker with high privileges. The CVE is not marked KEV, and the provided sources do not state active exploitation in the wild.

Researcher notes

Keep validation non-invasive. Focus on asset confirmation, firmware versioning, management-plane reachability, and privileged account review. The source bundle does not name a patch version, workaround, exploit availability, or affected products beyond UR32L v32.3.0.5.

Mitigation direction

  • Identify UR32L devices and confirm firmware versions.
  • Check Milesight guidance for fixed firmware or official remediation.
  • Limit HTTP management access to trusted administration networks.
  • Remove unnecessary high-privilege accounts and review administrator access.
  • Monitor for unexpected GRE or network configuration changes.

Validation and detection

  • Inventory Milesight UR32L devices across corporate and OT networks.
  • Verify whether any device runs firmware v32.3.0.5.
  • Confirm management HTTP interfaces are not internet-exposed.
  • Review admin account assignments for least-privilege gaps.
  • Check device logs for unusual configuration activity.
Prepared
Confidence
medium
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-25109 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-25109Attack 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.