Security readout for executives and security teams
Plain-English summary
CVE-2023-25106 is a high-severity memory corruption issue in Milesight UR32L v32.3.0.5. A highly privileged attacker could send a crafted HTTP request that may execute code on the device. This is most urgent where affected devices support critical connectivity or are reachable by administrative users over untrusted networks.
Executive priority
Treat this as a high-priority infrastructure hygiene issue, especially for exposed or critical UR32L deployments. The privilege requirement lowers broad opportunistic risk, but successful exploitation could fully compromise device confidentiality, integrity, and availability.
Technical view
The issue is a stack-based buffer overflow in the vtysh_ubus binary, caused by unsafe sprintf usage. The reported flaw is in set_gre handling of local_virtual_ip and local_virtual_mask. CVSS is 7.2: network reachable, low complexity, high privileges required, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to Milesight UR32L devices running v32.3.0.5. Risk depends heavily on whether the device HTTP management surface is reachable and whether attackers can obtain or use high-privilege credentials.
Exploitation context
The sources describe exploitation through a specially crafted HTTP request by an attacker with high privileges. The bundle does not show CISA KEV listing or other evidence of active exploitation in the wild.
Researcher notes
Evidence is specific to UR32L v32.3.0.5 and the vtysh_ubus set_gre code path. The provided sources do not name a patch version, workaround, or active exploitation. Avoid broadening impact to other Milesight models without additional vendor evidence.
Mitigation direction
- Identify all Milesight UR32L devices and firmware versions.
- Restrict HTTP management access to trusted administration networks only.
- Review Milesight and Talos guidance for fixed firmware or vendor mitigations.
- Rotate and harden privileged device credentials where exposure is possible.
- Monitor device management logs for suspicious privileged HTTP activity.
Validation and detection
- Confirm whether any UR32L devices run v32.3.0.5.
- Check whether administrative HTTP interfaces are internet-exposed or broadly reachable.
- Verify who has high-privilege access to affected devices.
- Review change logs or vendor advisories before applying firmware updates.
- Document compensating controls if no vendor fix is available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupExecution 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 lookupCVE-2023-25106 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.