LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25120: 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_dmvpn function with the cisco_secret variable.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Milesight UR32L routers running v32.3.0.5 contain a buffer overflow that can allow code execution after a highly privileged attacker sends a crafted HTTP request. This is not described as unauthenticated, but compromise could affect remote network access and site connectivity.

Executive priority

Treat as high priority for environments using UR32L routers in production, branch, or operational networks. It requires high privileges, which lowers broad exposure, but successful exploitation could execute code on a network device and disrupt connectivity or security boundaries.

Technical view

CVE-2023-25120 is a CWE-121 stack buffer overflow in the Milesight UR32L vtysh_ubus binary. Talos attributes it to unsafe sprintf use in set_dmvpn handling the cisco_secret variable. CVSS 3.1 is 7.2 with network access, low complexity, high privileges, and high CIA impact.

Likely exposure

Exposure appears limited to Milesight UR32L devices on firmware v32.3.0.5. Risk is highest where HTTP management is reachable from broad internal networks, VPN users, or the internet, and where privileged administrative credentials are available or compromised.

Exploitation context

The source bundle reports no CISA KEV listing and no cited evidence of active exploitation. The vulnerability is described as triggerable through crafted HTTP requests by an attacker with high privileges, so credential compromise materially changes risk.

Researcher notes

The provided evidence names one affected firmware version and one affected code path. It does not provide a confirmed fixed version, exploit-in-the-wild evidence, or broader product impact. Avoid assuming other Milesight models or firmware versions are affected without vendor confirmation.

Mitigation direction

  • Identify UR32L devices running firmware v32.3.0.5.
  • Check Milesight and Talos guidance for patched firmware or vendor mitigations.
  • Restrict HTTP management access to trusted administrative networks only.
  • Review and reduce privileged accounts able to manage affected devices.
  • Monitor affected devices for unexpected configuration changes or restarts.

Validation and detection

  • Confirm model and firmware version from asset inventory or device administration.
  • Verify management HTTP interfaces are not internet-exposed.
  • Review administrative account access and recent privileged login activity.
  • Check vendor advisories for fixed firmware availability before maintenance.
  • Track remediation evidence for each affected UR32L device.
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-25120 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-25120Attack 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.