LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25122: 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_openvpn_client function with the old_remote_subnet and the old_remote_mask variables.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-25122 is a high-severity memory corruption flaw in Milesight UR32L firmware v32.3.0.5. A highly privileged attacker can send a crafted HTTP request that may execute arbitrary code on the device. Business urgency is highest where these devices manage sensitive network connectivity or expose administration interfaces beyond tightly trusted users.

Executive priority

Treat as a targeted infrastructure risk, not a broad unauthenticated internet worm scenario. Prioritize affected devices that support critical connectivity, are remotely administered, or have many privileged users.

Technical view

The flaw is a CWE-121 stack-based buffer overflow in the vtysh_ubus binary, caused by unsafe sprintf usage. Talos reports the issue in set_openvpn_client involving old_remote_subnet and old_remote_mask variables. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, scoring 7.2.

Likely exposure

Exposure appears limited to Milesight UR32L devices running firmware v32.3.0.5. Risk depends on whether privileged HTTP administration access is reachable by attackers, contractors, compromised accounts, or adjacent internal systems.

Exploitation context

The sources describe arbitrary code execution via specially crafted HTTP requests, but require high privileges. The CVE is not marked as CISA KEV in the provided bundle, and no cited source states active exploitation.

Researcher notes

Evidence is strongest for affected product, version, vulnerability class, privilege requirement, and vulnerable function details. The bundle does not identify a fixed firmware version, public exploit availability, or active exploitation.

Mitigation direction

  • Inventory Milesight UR32L devices and identify firmware versions.
  • Check Milesight guidance for fixed firmware or official mitigation instructions.
  • Limit HTTP administration access to trusted management networks only.
  • Review and reduce highly privileged accounts on affected devices.
  • Monitor device logs for unusual OpenVPN configuration changes or admin activity.

Validation and detection

  • Confirm whether any UR32L device runs firmware v32.3.0.5.
  • Verify administrative HTTP interfaces are not internet-exposed.
  • Review access controls for users with high privileges.
  • Check configuration history for unexpected OpenVPN client changes.
  • Track vendor advisories until a confirmed fix is applied.
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-25122 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-25122Attack 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.