LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25111: 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 key variable.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25111 affects Milesight UR32L firmware v32.3.0.5. A privileged attacker who can reach the device over HTTP may trigger a buffer overflow that can lead to arbitrary code execution. This is high impact, but the provided sources indicate high privileges are required.

Executive priority

Prioritize remediation for production or remotely deployed UR32L devices, particularly those reachable from broad internal networks. Business urgency is high because successful exploitation could compromise device integrity and availability, but risk depends strongly on privileged access control.

Technical view

The flaw is a CWE-121 stack-based buffer overflow in the Milesight UR32L vtysh_ubus binary. Talos attributes it to unsafe sprintf usage in the set_gre function involving the key variable. The CVSS 3.1 score is 7.2, with network attack vector, low complexity, high privileges, no user interaction, and high CIA impact.

Likely exposure

Exposure is limited to Milesight UR32L devices running firmware v32.3.0.5, especially where HTTP management access is reachable by privileged users or compromised administrator accounts. The source bundle does not support extending impact to other products or versions.

Exploitation context

The sources state that a specially crafted HTTP request from a high-privileged attacker can trigger arbitrary code execution. CISA KEV status is false in the bundle, and the provided evidence does not establish active exploitation or public weaponization.

Researcher notes

Validation should stay within authorized lab or defensive review boundaries. Focus on UR32L v32.3.0.5, vtysh_ubus, set_gre, and the key variable. The provided sources do not name a patch level, workaround, or affected range beyond v32.3.0.5.

Mitigation direction

  • Identify all Milesight UR32L devices and confirm firmware versions.
  • Check Milesight and Talos guidance for fixed firmware or official mitigations.
  • Restrict HTTP management access to trusted administrative networks only.
  • Review and reduce privileged accounts with device management access.
  • Monitor for unexpected configuration changes or privileged management activity.

Validation and detection

  • Inventory UR32L assets and verify whether firmware v32.3.0.5 is present.
  • Confirm HTTP management interfaces are not exposed to untrusted networks.
  • Review device access logs for unusual privileged HTTP management activity.
  • Track vendor advisories for patch availability and remediation instructions.
  • Do not assume other Milesight models are affected without vendor evidence.
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-25111 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-25111Attack 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.