LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25096: 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_qos function with the rule_name variable with two possible format strings.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects Milesight UR32L routers running firmware v32.3.0.5. A highly privileged attacker could send crafted HTTP requests that trigger buffer overflows and potentially run code on the device. The business concern is highest where these routers manage network connectivity or remote sites and administrative access is exposed or weakly controlled.

Executive priority

Treat this as a high-priority network appliance issue if UR32L devices are deployed. It is not listed as known exploited in the provided data, but successful abuse could compromise the device and affect network integrity, availability, and confidentiality.

Technical view

CVE-2023-25096 is a CWE-121 stack buffer overflow in the Milesight UR32L vtysh_ubus binary. Talos attributes it to unsafe sprintf usage in set_qos using the rule_name variable with two format-string paths. The CVSS 3.1 score is 7.2: network reachable, low complexity, high privileges required, no user interaction, full CIA impact.

Likely exposure

Known exposure is limited to Milesight UR32L version v32.3.0.5 based on the provided sources. The main risk is devices where privileged web or HTTP management access is reachable by administrators, service accounts, or attackers who obtain high privileges.

Exploitation context

The source bundle says a specially crafted HTTP request can lead to arbitrary code execution, but requires high privileges. The bundle marks KEV as false and provides no cited evidence of active exploitation in the wild.

Researcher notes

The strongest technical evidence comes from Talos TALOS-2023-1716 and the CVE record. The provided bundle does not name a patch version, workaround, public exploit, or exploitation campaign, so remediation should be tied to current vendor guidance rather than assumed fixes.

Mitigation direction

  • Identify any Milesight UR32L devices running firmware v32.3.0.5.
  • Check Milesight and Talos guidance for fixed firmware or official mitigations.
  • Restrict administrative HTTP management access to trusted networks only.
  • Review and tighten privileged accounts used to manage affected devices.
  • Monitor affected devices for unusual privileged configuration activity.

Validation and detection

  • Confirm model and firmware version on all Milesight UR32L assets.
  • Verify administrative web access is not exposed to untrusted networks.
  • Review device access logs for unexpected privileged HTTP management activity.
  • Confirm whether vendor guidance or a firmware update has been applied.
  • Document any affected devices that cannot be immediately remediated.
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-25096 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-25096Attack 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.